Skip to main content
Glama

check_component_compatibility

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.

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>",
      "powder": "<powder>"
    },
    "name": "check_component_compatibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
powderYes
bullet_grNoBullet weight in grains (optional; enables corpus-membership answer)
cartridgeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the discovery burden and does well: it declares read-only scope implicitly, explains the membership rule (nearest-bullet), and clearly states what is not returned (no charge/velocity/pressure numbers, rights-class restriction). It omits failure behaviour — e.g. what happens when the pair does not resolve — which keeps it below 5.

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 opening sentence is well front-loaded and specific, but the remainder repeats the same scope claim twice ('Answers membership and canonical identity ONLY' and 'Identity + published dimensional metadata only — NOT load data'), and the CAPS jargon makes it denser than needed. It is not padded with fluff, but the redundancy costs it.

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 three-parameter read tool with no output schema, the description gives enough to call it correctly: inputs are a cartridge, a powder, and optional bullet weight, and the return is identity plus published dimensional metadata rather than ballistic numbers. Only the non-resolving/error path remains unspecified.

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 only 33%, so the description is expected to compensate for two undocumented parameters. It explains the bullet_gr concept indirectly through 'nearest-bullet membership' and the corpus-membership answer, but never describes what the cartridge and powder strings should look like or how a bad value is handled.

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 states a specific verb (check) and a precise resource (whether a cartridge+powder pair resolves in the database and has a reference-corpus row). Phrases like 'nearest-bullet membership' and 'canonical identity' carve out a distinct scope from siblings such as solve_internal_ballistics or generate_load_ladder, though no sibling is named directly.

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 through exclusion ('Answers membership and canonical identity ONLY') and a warning against expecting load data, which lets an agent infer this is a pre-flight check. However, there is no explicit when-to-use statement, no prerequisite ('resolve' requires the pair to be in the served DB), and no named alternative for agents who actually want numbers.

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