Skip to main content
Glama

solve_internal_ballistics

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "caliber": "<caliber>",
      "bullet": "<bullet>",
      "powder": "<powder>",
      "charge_gr": "<charge_gr>",
      "barrel_len_in": "<barrel_len_in>"
    },
    "name": "solve_internal_ballistics"
  }
}

Input Schema

NameRequiredDescriptionDefault
bulletYesProjectile display name ('Mfr Product (W gr)') or projectile.csv id
powderYesPropellant name ('Alliant Blue Dot') or propellant.csv id
primerNoPrimer identity — accepted for forward compatibility; the engine does not model primers yet
caliberYesCartridge name or caliber.csv id
charge_grYesPowder charge in grains (sanity bounds 0.1..200)
weight_grNoBullet weight override in grains (optional). For cast bullets: same mold, different alloy, different weight (a LEE C358-158-SWC can drop 137 gr in pewter/tin vs 158 gr catalog nominal). None = catalog nominal. >20% off nominal emits BULLET_WEIGHT_OUTLIER.
firearm_typeNoRevolver cylinder-gap override: 'auto' (default, engine detects from caliber name), 'revolver', or 'not_revolver' (rifle/pistol)
barrel_len_inYesBarrel length in inches
powder_temp_cNoPowder temperature in °C (optional; -29..+49 validated band, clamped outside). None = ambient (default).
cartridge_oal_inNoCartridge overall length in inches (default: caliber max OAL)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / barrel_len_in / exclusiveMinimum
      Removed value: -0.5
    • addedInput schema / properties / barrel_len_in / minimum
      Added value: +0.5
    • changedInput schema / properties / weight_gr / anyOf
      Previous value: -[
      -  {
      -    "exclusiveMinimum": 1,
      -    "maximum": 2000,
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "maximum": 2000,
      +    "minimum": 1,
      +    "type": "number"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden and does so thoroughly: it discloses the safety envelope, accuracy error rates, pressure-field caveats, and the prohibition on treating results as published load data. It also explains the non-removable warnings and why verdicts must be treated as relative rather than absolute.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense and front-loads the core purpose, accuracy caveats, alternative tool, and safety policy in a logical order. It is long, but most of the length is justified by the safety-critical domain and the absence of annotations; there is some redundancy in the repeated safety framing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a complex solver with no annotations and no output schema, the description supplies the missing behavioral context: return envelope contents, pressure-field interpretation, accuracy limitations, and safety instructions. It is sufficiently complete for an agent to call the tool and correctly frame the result to a user.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already explains each of the 10 parameters in detail. The description adds limited parameter-level meaning beyond the opening reference to an exact cartridge/bullet/powder/charge specification, so it meets but does not exceed the baseline for fully documented schemas.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: solve one internal-ballistics point for an exact cartridge/bullet/powder/charge specification. It clearly frames the output as modeled velocity/energy/pressure wrapped in a safety envelope, and it distinguishes this tool from generate_load_ladder for load development.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says to prefer generate_load_ladder for load development, which is a clear when-not-to-use and alternative-tool routing statement. The single-point solving use case is also clearly implied by the opening sentence, leaving little ambiguity about when this tool is appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources