Skip to main content
Glama

generate_load_ladder

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.

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>",
      "barrel_len_in": "<barrel_len_in>"
    },
    "name": "generate_load_ladder"
  }
}

Input Schema

NameRequiredDescriptionDefault
bulletYesProjectile display name or projectile.csv id
powderYesPropellant name or propellant.csv id
primerNoPrimer identity — accepted for forward compatibility
caliberYesCartridge name or caliber.csv id
n_rungsNoNumber of ladder rungs (3–10, default 7)
charge_grNoCurrent charge (enables sensitivity + next-rung marker)
firearm_typeNoRevolver cylinder-gap override: 'auto' (default), 'revolver', or 'not_revolver' (rifle/pistol)
barrel_len_inYesBarrel length in inches
powder_temp_cNoPowder temperature in °C (optional; -29..+49 validated band)
cartridge_oal_inNoCartridge overall length in inches (default: caliber max OAL)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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
  2. First observed

TDQS

A4/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and discharges it well: it discloses the auth requirement (anonymous refused pre-compute), the refusal behavior (coarse requests refused, never silently interpolated), that the return envelope matches POST /v1/ladder, and detailed safety/pressure-field semantics. This is substantive behavior an agent could not infer from structured fields alone.

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

Conciseness3/5

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

The key purpose and "PREFERRED" signal are front-loaded, which is good, but the safety block is long and dense, and much of the pressure-field derivation reads as policy boilerplate that expands the definition considerably. It is informative but not tight.

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

Completeness4/5

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

For a 10-parameter, no-output-schema, no-annotation tool, the description covers auth, refusal codes, return envelope, and safety semantics well enough for correct invocation. The remaining gap is the rung-count tension with the schema, which is not resolved.

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 documents all 10 parameters and the baseline is 3. The description adds little param-level detail and even introduces tension by demanding ">=5 rungs" while the schema allows n_rungs minimum 3, which could confuse an agent deciding what to send.

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

Purpose4/5

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

The description uses a specific verb+resource ("generate a work-up ladder") and frames it as "PREFERRED for load development," which steers the agent away from the sibling single-point solve_internal_ballistics. It stops short of naming an alternative explicitly, so it is clear but not fully sibling-differentiated.

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

Usage Guidelines4/5

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

"PREFERRED for load development" plus the auth prerequisite and the LADDER_TOO_COARSE refusal set clear context for when to reach for it. It never states an explicit "use X instead when..." exclusion, so the boundary with siblings is implied rather than spelled out.

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