Skip to main content
Glama

get_cartridge_spec

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.

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": {
      "cartridge": "<cartridge>"
    },
    "name": "get_cartridge_spec"
  }
}

Input Schema

NameRequiredDescriptionDefault
cartridgeYesCartridge name, CIP name, alternate name, or numeric id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden, and it does disclose the serving census ('mode != hidden AND geloescht == 0'), meaning hidden or deleted cartridges are invisible to the lookup. It also states the rights-class discipline limiting output to identity and dimensional metadata. Missing: behavior on a miss (empty vs error) and any indication this is purely read-only.

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?

One dense sentence plus a scoping clause; the essential lookup scope is front-loaded and nothing is padding. The parenthetical census expression and em-dash enumerations make it slightly heavy for a one-parameter read tool, but every element carries information.

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 single-parameter, no-output-schema read tool this is nearly sufficient: it names the return fields, the lookup keys and the record-visibility filter. The only real gap is miss/ambiguity behavior, which matters given the tool requires exactly one cartridge.

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 coverage is 100% and the single parameter's schema description already lists exactly the accepted forms (name, CIP name, alternate name, numeric id). The description repeats rather than extends that, adding no format or disambiguation detail such as how ambiguous names resolve.

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?

States a specific verb and resource ('Look up ONE cartridge in the served component database') and enumerates the lookup keys (name, CIP name, alternate name, id) plus the returned fields (pmax_bar, case volume, bore/case dimensions, max OAL). It explicitly rules out load data, which cleanly separates it from the ballistics/load siblings.

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?

Gives a clear when-not: 'NOT load data ... no charge/velocity/pressure values are served by this tool', which routes the agent away from using it for load questions. It does not name the alternative tool to use for that case (e.g. solve_internal_ballistics or generate_load_ladder), so it stops short of full alternative 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