Skip to main content
Glama

Server Details

Physics interior-ballistics solver: solves, ladders, trajectory, lookups. Published error rates.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
ChatGPT
–
Claude
–

TDQS

A3.7/5.0

Scored across 6 tools

Disambiguation4/5

Each tool has a distinct role: identity/membership lookup (check_component_compatibility, get_cartridge_spec), enumeration (list_powders), single-point solve, ladder generation, and exterior trajectory. The closest overlap is solve_internal_ballistics vs generate_load_ladder, but the descriptions explicitly route development work to the ladder tool. Minor residual ambiguity between the pair-membership check and the cartridge spec lookup, since both return identity/metadata.

Naming Consistency4/5

Five of six names follow a clean verb_noun pattern (check_component_compatibility, generate_load_ladder, get_cartridge_spec, list_powders, solve_internal_ballistics). The outlier is the bare noun 'trajectory', which breaks the pattern but is still unambiguous in meaning.

Tool Count5/5

Six tools is a tight, well-scoped surface for an internal/exterior ballistics server: lookup, enumeration, compatibility check, single solve, ladder, and trajectory. Each tool covers a distinct computation stage with no filler.

Completeness3/5

The solver and trajectory tools require an exact bullet spec, yet there is no tool to list or search bullets, and no way to enumerate/search cartridges (only exact-name or id lookup). Identity, solve, ladder, and trajectory stages are covered, but the component-discovery gap will cause agent dead ends when building a full solve request.

Available Tools

6 tools
check_component_compatibilityAInspect

Check whether a cartridge+powder pair RESOLVES in the served database and whether the published-reference corpus contains a row for the pair (nearest-bullet membership — the same membership that decides a ladder's basis). Answers membership and canonical identity ONLY; it never serves the corpus row's numbers. Identity + published dimensional metadata only — NOT load data (rights-class discipline): no charge/velocity/pressure values are served by this tool.

Inputs: powder (required), cartridge (required), bullet_gr.

generate_load_ladderAInspect

PREFERRED for load development: generate a work-up ladder (>=5 rungs required — coarser requests are refused LADDER_TOO_COARSE, never silently interpolated) from the published-reference or charge-only bookends down, with per-rung trajectory nodes and the full safety envelope. Requires an API key or subscriber token — anonymous callers are refused pre-compute. Returns the SAME envelope as POST /v1/ladder. SAFETY (verbatim policy): Returns modeled pressure and velocity from a physics solver, plus a safety envelope. This is NOT published load data. Always present the envelope, warnings, and disclaimer to the user; never state a single charge weight as a recommendation. Pressure fields (p_max_bar, p_max_psi, saami_max_bar) are modeled compliance-vs-SAAMI-ceiling indicators on the model's CUP-equivalent scale, while pressure_percent_saami is reported piezo-equivalent: the percent equals p_max_bar x 1.2783 / saami_max_bar, so it is NOT peak / ceiling as served. The factor compensates a measured model under-drive on transducer anchors; the pure CUP-to-piezo convention component is bounded near 4-8%, and the remainder is genuine under-drive retained so an over-max load cannot read safe. Not measured proof pressures and not accuracy-validated numbers: the validation corpus is velocity-only. Treat them as position relative to the ceiling, with real-world spread unknown. not_for_loading_decisions_without_published_data: this result is a model output. Do not work up a load from it alone — cross-check against published data for your exact components before loading.

Inputs: bullet (required), powder (required), caliber (required), barrel_len_in (required), +6 more.

get_cartridge_specAInspect

Look up ONE cartridge in the served component database (census: mode != 'hidden' AND geloescht == 0) by name, CIP name, alternate name, or id — returns the published dimensional spec (pmax_bar, case volume, bore/case dimensions, max OAL). Identity + published dimensional metadata only — NOT load data (rights-class discipline): no charge/velocity/pressure values are served by this tool.

Inputs: cartridge (required).

list_powdersAInspect

List propellants in the served database (optionally filtered by manufacturer substring), with the GRT attributes the solver uses (Ba, Qex). Identity + published dimensional metadata only — NOT load data (rights-class discipline): no charge/velocity/pressure values are served by this tool.

Inputs: manufacturer.

solve_internal_ballisticsAInspect

Solve one internal-ballistics point: modeled velocity/energy/pressure for an exact cartridge+bullet+powder+charge specification, wrapped in the non-removable safety envelope (charge range, closed-enum warnings, assumptions). Returns the SAME envelope as POST /v1/solve. Measured accuracy: velocity averages about 7.5% error against 30,327 published loads; the pressure a user sees displayed reads 7.38% low against printed CUP figures and 0.91% low against printed psi figures at the median, so verdicts are relative — start low and work up. For load DEVELOPMENT prefer generate_load_ladder (a work-up ladder with per-rung nodes). SAFETY (verbatim policy): Returns modeled pressure and velocity from a physics solver, plus a safety envelope. This is NOT published load data. Always present the envelope, warnings, and disclaimer to the user; never state a single charge weight as a recommendation. Pressure fields (p_max_bar, p_max_psi, saami_max_bar) are modeled compliance-vs-SAAMI-ceiling indicators on the model's CUP-equivalent scale, while pressure_percent_saami is reported piezo-equivalent: the percent equals p_max_bar x 1.2783 / saami_max_bar, so it is NOT peak / ceiling as served. The factor compensates a measured model under-drive on transducer anchors; the pure CUP-to-piezo convention component is bounded near 4-8%, and the remainder is genuine under-drive retained so an over-max load cannot read safe. Not measured proof pressures and not accuracy-validated numbers: the validation corpus is velocity-only. Treat them as position relative to the ceiling, with real-world spread unknown. not_for_loading_decisions_without_published_data: this result is a model output. Do not work up a load from it alone — cross-check against published data for your exact components before loading.

Inputs: bullet (required), powder (required), caliber (required), charge_gr (required), +6 more.

trajectoryBInspect

Trajectory / drop table: point-mass (3-DOF) exterior solve fed by the modeled muzzle velocity for an exact cartridge+bullet+powder+charge spec (or an explicit muzzle_velocity_fps override). Returns range rows (drop, velocity, energy, windage) plus the model assumptions. Beta keys get the table to 300 yd (the same PREFIX the web free tier gets); subscriber keys get the full table. No pressure figures on this surface. SAFETY (verbatim policy): Returns modeled pressure and velocity from a physics solver, plus a safety envelope. This is NOT published load data. Always present the envelope, warnings, and disclaimer to the user; never state a single charge weight as a recommendation. Pressure fields (p_max_bar, p_max_psi, pressure_percent_saami, saami_max_bar) are modeled compliance-vs-SAAMI-ceiling indicators, not measured proof pressures and not accuracy-validated numbers: the validation corpus is velocity-only. Treat them as position relative to the ceiling, with real-world spread unknown. not_for_loading_decisions_without_published_data: this result is a model output. Do not work up a load from it alone — cross-check against published data for your exact components before loading.

Inputs: bullet (required), powder (required), caliber (required), charge_gr (required), +16 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      F
      maintenance
      Provides 55 specialized tools for precise physics calculations and rigid-body simulations, covering mechanics, fluid dynamics, and rotational motion. It enables LLMs to perform realistic motion analysis and trajectory modeling with support for real-world factors like drag, wind, and altitude.
      62
      14
      Apache 2.0
    • A
      license
      B
      quality
      B
      maintenance
      Enables MCP clients and LLM agents to run deterministic fast-reactor and fuel-cycle solvers in one place: sodium bundle thermal hydraulics with FCCI margins, RVACS decay-heat transients, heat-pipe/sCO2 capillary limits, LiCl-KCl electrorefining mass balance, Ac-225 isotope yield, data-center microgrid load-following, defense microreactor resilience, and HALEU cask logistics. Exposes a chained multi-physics transient orchestrator tool alongside a standalone CLI for scripted physics runs.
      11
      Academic Free v1.1
    • A
      license
      A
      quality
      B
      maintenance
      Deterministic mathematical calculation engine providing 446 verified analytical solvers across engineering, finance, geometry, and science for AI agents.
      2
      12
      321 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Deterministic physics plausibility checks for LLM outputs: validates numeric claims against physical law, checks single quantities (speed, temperature, energy bounds), and validates robotics dataset records. Offline subset of the PHM engine; zero external services.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources