Add MCP entry point for NARP reliability tools

[839651726]

Summary

• Introduce NARP/narp_mcp.py. It exposes one FastMCP server and registers the tool functions with power_mcp_tool, following the layout used by the other integrations.

Why

• This change lets PowerMCP users call the NARP reliability analysis server directly from the repo. The workflow now matches the other MCP tools, and the README gives concrete prompts for MCP clients.

Testing

• Manual run: python -m NARP.narp_mcp to confirm the FastMCP server starts and registers the tools.
• Use the README prompts in an MCP-enabled client to call validate_input, run_simulation_sync, etc., and check the responses.

[qian-harvard]

Could you only keep 1 or 2 case files to make the code clean? Also, please add some intro to NARP since it is not commonly known for engineers without a reliability background.

[839651726]

Thanks for the review. I updated the branch to address both comments.

Case files cleanup

I trimmed the bundled NARP data to a minimal example set and removed large test/integration datasets from this PR, so the integration stays clean and lightweight.

Now the branch keeps one runnable sample case at NARP/examples/case1 with only the required input artifacts:

• ZZMC.csv
• ZZUD.csv
• ZZLD.csv
• ZZTD.csv
• ZZTC.csv
• LEEI

NARP introduction for non-reliability users

I added a “What is NARP?” section in NARP/README.md with a concise overview of:

• What NARP does (resource adequacy / reliability assessment)
• Key indices (LOLE, HLOLE, EUE)
• Typical planning and maintenance-study use cases

I also updated usage examples to reference the minimal bundled case and aligned the MCP server README examples accordingly.

[qian-harvard]

@839651726 Can you update your PR based on the new main branch?