Pterasim MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pterasim.simulateB | Generate aerodynamic coefficients with UVLM fallback. Supply wing geometry, flapping schedule, and timestep count. Returns forces, torques, and solver metadata. Example: {"span_m":0.8,"chord_m":0.12,"num_timesteps":180} |
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 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool has a clear, singular purpose focused on aerodynamic simulation with specific inputs and outputs.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'pterasim.simulate' follows a clear and logical pattern that would be consistent if more tools existed.
A single tool is too few for a server named 'Pterasim MCP Server', which suggests a broader aerodynamic simulation domain. This minimal toolset limits functionality and likely leaves significant gaps in coverage.
The server appears to focus on aerodynamic simulation, but with only a simulate tool, there are obvious gaps. Missing operations might include geometry creation, parameter analysis, result visualization, or data export, making the surface incomplete for typical simulation workflows.