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.mesh_sensitivityA | Compare a fixed flight condition across 2-8 increasing mesh factors starting at 1. Refine surface chord/span counts on staged copies; body discretization stays fixed. Preflight every mesh against the configured vortex budget. Save coefficients, baseline/adjacent differences, JSON, CSV and Markdown with one total timeout. Optional absolute tolerances only assess the final adjacent difference; no automatic mesh-convergence claim, Richardson extrapolation, or geometry suitability proof. |
| avl.prepare_trimA | Convert explicit SI mass/weight, density and speed to target CL without running AVL. Require geometry length units and a CG with units; set the moment reference to CG. Return a TrimRequest and References usable in trim/sweep/submit, plus provenance. Assumes unbanked steady level lift=weight, zero beta/rates and target Cm=0. Mach is supplied separately; no inferred atmosphere, thrust balance or inertia model. |
| avl.trim_physicalA | Prepare lift=weight and zero pitching moment about explicit CG, then verify trim. Takes SI mass/weight, density and speed plus declared geometry/CG length units. Solves alpha and one CONTROL with bounds/residual checks and independent replay. Save dimensional inputs and conversion provenance with native results, including numerical failures. Mach remains explicit. No thrust balance, mass file or eigenmodes. |
| avl.sweepA | Supply exactly one of conditions or trim_requests, each containing 1-10000 cases. Prescribed conditions share AVL processes grouped by Mach, resetting rates/controls. Trim requests run sequentially: each solves alpha/CONTROL for CL/Cm and independently replays in a fresh process. All cases and replays share one total timeout budget. Return cases in requested order with trim residuals, bounds and verification metadata. 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. Supply exactly one of conditions or trim_requests. Every trim requires its own fresh verification; cancel interrupts candidate/replay and resume reuses verified cases only. 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 14 tools
Most tools have clearly distinct roles: single-case run, multi-case sweep, detached submit, and job control/status/results are readily separable. The main ambiguity is within the trim family (prepare_trim, trim, trim_physical), though their descriptions clarify whether AVL is executed and what inputs are required.
All names use lower snake_case under the avl. namespace, which is consistent at the lexical level. However, the set mixes imperative verbs (run, sweep, submit, inspect) with noun-like resource names (status, results, health) and compound descriptive forms (mesh_sensitivity, trim_physical), so it is readable but not a predictable verb_noun convention.
Fourteen tools is well within the appropriate range for a complex AVL analysis server. Each major phase—inspection, validation, execution, background job control, and result retrieval—has a dedicated tool without obvious filler.
The surface covers the core AVL lifecycle: inspect/validate/health, trim preparation, run/sweep/submit, status/cancel/resume, and results retrieval. Minor gaps such as a job-list operation or explicit geometry/setup management are not central to the apparent analysis scope, but there is no obvious dead end.