tigl-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 |
|---|---|
| pingA | Lightweight health check that confirms the server is reachable without requiring a CPACS session or TiGL runtime. |
| open_cpacsB | Open a CPACS session from a file path or an XML string. |
| close_cpacsC | Close a CPACS session and free resources. |
| get_configuration_summaryC | Return component lists and the overall bounding box. |
| check_geometryA | Check the aircraft's geometry, as real TiGL builds it, against the file: a wing on one side only, a wing not touching the fuselage, a reference area that cannot belong to the largest wing. Returns the findings (each with severity 'fault', the component, what was measured and the tolerance) and the per-component bounding boxes. Run it after opening a file and before meshing. |
| list_geometric_componentsC | List CPACS geometric components. |
| get_component_metadataC | Return metadata for a geometric component. |
| export_component_meshC | Export a component mesh as base64-encoded content. |
| export_configuration_cadA | Export the full configuration CAD (or a single component when component_uid is set) to a file and return its path as cad_path. Pass cad_path to su2_generate_mesh_from_step as step_path. Set include_base64 only if the file content itself is needed. |
| get_high_level_parametersC | Return high-level design parameters for a component. |
| set_high_level_parametersB | Record high-level design parameter values in this session's parameter table. Does NOT modify the CPACS geometry: CAD export and CFD still use the original shape (see applies_to_geometry). |
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 11 tools
Each tool maps to a distinct action or resource: session lifecycle (open/close/ping), inspection (summary, list, metadata, parameters), validation (check_geometry), and export (mesh vs CAD). The only mild overlaps are get_configuration_summary vs list_geometric_components and export_component_mesh vs export_configuration_cad, but the descriptions clearly separate them by scope (overview vs enumeration) and by output form (base64 mesh vs file-path CAD).
Nearly every name follows a consistent snake_case verb_noun pattern (get_configuration_summary, open_cpacs, close_cpacs, check_geometry, list_geometric_components, set_high_level_parameters). The only deviation is the bare verb 'ping', which is a conventional exception rather than an inconsistency.
Eleven tools fit cleanly into the 3-15 well-scoped range for a CPACS/TiGL geometry server. Each tool corresponds to a distinct stage of the workflow (open a session, inspect, validate, export), and none appears redundant.
The surface covers the full session lifecycle, component inspection, geometry validation, mesh/CAD export, and parameter read/write, which is solid coverage for the stated domain. The main gap is that set_high_level_parameters explicitly does not modify geometry, so there is no path for applying parameter changes or re-evaluating the shape, which limits a natural design-iteration workflow.