avl-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AVL_BIN | Yes | Path to the AVL 3.52 executable. Equivalent to the --avl-bin command line argument. | |
| AVL_MCP_WORK_ROOT | Yes | Directory for runs, jobs, and saved results. Equivalent to the --work-root command line argument. | |
| AVL_MCP_INPUT_ROOT | No | Optional root directory that approved model files must resolve inside. Equivalent to the --input-root command line argument. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| avl.healthA | Diagnose Python/native dependencies, architecture, directory permissions and AVL startup. Save evidence. Numerical validation and desktop registry refresh remain separate. |
| avl.inspectA | Read geometry, references, controls and dependencies; original files are unchanged. |
| avl.validateA | Validate supported text grammar, dependencies and mesh limits. No solver execution. |
| avl.runA | Run one prescribed flight condition. Return forces, ST/SB derivatives, surface loads and links to strip CSV/JSON. Angles in degrees, rates nondimensional BODY axes; CONTROL values use gains defined in geometry. Default controls/rates zero. A references override changes only the staged copy. Ignores nearby .run/.mass. |
| avl.trimA | Solve alpha and one existing CONTROL for target CL/Cm at zero beta/body rates. CONTROL values retain section gains, not automatically physical deflection degrees. Bounds accept/reject the native solution, not constrain iterations. Success requires residual/bounds checks and a fresh fixed-condition solve. Moments use the explicit geometry/override reference point, not an inferred CG. No mass/thrust balance. |
| avl.sweepA | Run 1-10000 conditions in shared AVL processes, grouped by Mach, within one budget. Return cases in requested order; reset all rates and controls at every condition. Select outputs (total is always retained); None preserves all previous tables. Preserve successful and failed cases and write summary.csv. For long jobs use submit. Return partial results and isError=true if any requested case is unsuccessful. |
| avl.submitA | Snapshot inputs and start a detached local AVL job; return job_id immediately. 1-10000 cases, at most two background workers execute per work root. Workers survive MCP client disconnection. Timeout is the execution budget per attempt, excluding queue. outputs=['total'] skips derivatives/surface/strip output; None requests all tables. |
| avl.statusB | Read queued/running/completed/failed/cancelled/interrupted state and case counts. success=true means the status was read; inspect state/error for solver outcome. |
| avl.cancelA | Request cooperative cancellation of this job's worker and its owned AVL process. Completed cases and logs remain. Query status until cancellation is acknowledged. |
| avl.resumeA | Resume an inactive job after verifying input, solver, implementation and output hashes. Recompute only failed, missing or damaged cases. Active jobs cannot be resumed. |
| avl.resultsA | Page saved background or run/sweep results without running AVL. Limit 1-100 cases. Filter by original zero-based indices and dotted fields, e.g. total.fields.CLtot, body.derivatives.Cmq, stability.control_derivatives.elevator.Cm. Missing tables return FIELD_NOT_AVAILABLE; raw/strip artifact paths remain available by default. |
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
Most tools have clearly distinct purposes, but the execution-related tools avl.run, avl.sweep, and avl.submit overlap in that all run AVL cases with different execution models. Descriptions clarify the boundaries (single condition vs. many conditions vs. detached background job), so an agent can disambiguate after reading carefully.
All tools follow a highly predictable avl.<action> pattern with lowercase single words and no mixed conventions. The only minor inconsistency is that some actions are verbs (run, validate, inspect) and others are nouns (health, status, results), but this is negligible and does not impair selection.
The server exposes 11 tools, which is well within the recommended 3-15 range and appropriate for an AVL analysis domain. The background job lifecycle tools (submit, status, cancel, resume) earn their place because AVL runs can be long-lived and need detached execution support.
The surface covers validation, inspection, single-run execution, trim, sweeps, background job management, results retrieval, and health checks, which is a strong lifecycle for running AVL analyses. Minor gaps exist, such as no explicit tool to list all background jobs or to modify/author geometry, but agents can work around these by managing jobs individually and relying on external file editing.