pycycle-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pingB | Simple healthcheck for the pyCycle MCP server. |
| create_cycle_modelB | Instantiate a pyCycle/OpenMDAO Problem for a specified engine cycle. |
| close_cycle_modelA | Close a pyCycle session and free resources. |
| get_cycle_summaryB | Return a succinct summary of the current cycle model. |
| list_variablesC | List variables in the cycle model. |
| set_inputsB | Set one or more input variables in the cycle model. |
| get_outputsA | Fetch values for one or more outputs after a run. |
| run_cycleC | Run the cycle model and return selected outputs. |
| sweep_inputsC | Perform a parametric sweep over input variables. |
| compute_totalsC | Compute total derivatives using OpenMDAO. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool has a clearly distinct purpose: lifecycle management (create/close), configuration (set_inputs), execution (run_cycle, sweep_inputs), analysis (compute_totals, get_outputs), and introspection (get_cycle_summary, list_variables). No two tools overlap ambiguously.
All tool names follow a consistent verb_noun snake_case pattern (e.g., create_cycle_model, run_cycle, compute_totals). The naming is predictable and uniform across the entire set.
With 10 tools, the set is well-scoped for a cycle modeling server. Each tool covers a necessary operation without redundancy, fitting comfortably within the ideal 3-15 tool range.
The tool surface provides comprehensive lifecycle coverage: create, configure, run, analyze (including sweeps and derivatives), retrieve results, and close. No obvious dead ends or missing core operations for the domain.