Skip to main content
Glama

trajectory

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.

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": "trajectory"
  }
}

Input Schema

NameRequiredDescriptionDefault
bulletYesProjectile display name ('Mfr Product (W gr)') or projectile.csv id
powderYesPropellant name or propellant.csv id
primerNo
temp_cNo
caliberYesCartridge name or caliber.csv id
step_ydNo
wind_mphNoFull-value crosswind, left -> right
bc_lb_in2NoBallistic coefficient override; default = catalog g7bc (else g1bc) for the bullet
charge_grYesPowder charge in grains
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_typeNo
max_range_ydNo
pressure_hpaNo
barrel_len_inYesBarrel length in inches
drag_functionNoDrag standard of `bc_lb_in2`; default G1 for an override, otherwise whichever catalog BC was used
powder_temp_cNo
zero_range_ydNo
sight_height_inNo
cartridge_oal_inNo
muzzle_velocity_fpsNoOverride; default = the engine's v_max_fps for this load

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

B3.2/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does substantial work: it discloses tier gating (Beta keys truncated to 300 yd, subscriber keys get the full table), states that model assumptions are returned, and warns that the validation corpus is velocity-only. The one serious defect is internal inconsistency — it first says 'No pressure figures on this surface' and then describes p_max_bar, p_max_psi, pressure_percent_saami and saami_max_bar in detail, text that appears copied from the internal-ballistics tool and leaves the agent unsure whether pressure is returned here.

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

Conciseness2/5

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

The useful first sentence is followed by a large block of safety boilerplate, much of which is irrelevant to this surface (a verbatim pressure-field policy for fields the description says are not returned) plus a pasted 'not_for_loading_decisions_without_published_data' token. The signal-to-noise ratio is poor and the self-contradicting pressure paragraph actively costs the reader effort.

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

Completeness3/5

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

Return shape is covered (range rows plus model assumptions) even though there is no output schema, and the tier-limit behavior is disclosed, which is valuable for a 20-parameter tool. However, with no annotations and half the parameters undocumented, the definition leaves too much of the calling contract unexplained, and the contradictory pressure paragraph muddies rather than completes the picture.

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

Parameters2/5

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

Twenty parameters with only 50% schema description coverage means roughly ten inputs (primer, temp_c, powder_temp_c, sight_height_in, zero_range_yd, firearm_type, pressure_hpa, step_yd, max_range_yd, cartridge_oal_in) are undocumented in both the schema and the description. The prose only restates what the schema already says about muzzle_velocity_fps and the cartridge/bullet/powder/charge inputs, adding essentially no new meaning.

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 opening sentence names a specific computation ('point-mass (3-DOF) exterior solve') and its inputs ('modeled muzzle velocity for an exact cartridge+bullet+powder+charge spec'), and it enumerates the returned columns (drop, velocity, energy, windage). The word 'exterior' implicitly separates it from solve_internal_ballistics, but no sibling is named explicitly, so an agent must infer the boundary.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the tool produces a range table for a known load, and the muzzle_velocity_fps override is offered as an alternative input path. There is no explicit 'use this instead of X when Y' guidance against generate_load_ladder or solve_internal_ballistics, and the cross-check instruction is framed as safety policy rather than tool routing.

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