Skip to main content
Glama

External gear pair

bpj_eng_gear_pair
Read-onlyIdempotent

Calculate speed ratio and output speed of one external mesh from tooth counts and drive rpm.

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": {
      "driver": "<driver>",
      "driven": "<driven>",
      "rpm": "<rpm>"
    },
    "name": "bpj_eng_gear_pair"
  }
}

Input Schema

NameRequiredDescriptionDefault
rpmYes
drivenYes
driverYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare this as a read-only, idempotent, non-destructive, closed-world computation, so the safety profile is fully covered structurally. The description adds that the result comprises 'speed ratio and output speed' from tooth counts plus drive rpm, which is real value given the absence of an output schema, but it never defines the direction of the ratio (driven/driver vs. driver/driven), which is the main ambiguity for a numeric computation.

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

Conciseness5/5

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

A single front-loaded sentence with no filler, hedging, or restatement of the title. Every clause ('speed ratio', 'output speed', 'tooth counts', 'drive rpm') contributes distinct 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 simple, three-parameter, single-formula calculator with no output schema and full annotation coverage, the definition supplies enough to invoke it correctly and to know roughly what comes back. The only meaningful gap is the ratio convention, which matters for interpreting the numeric result.

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

Parameters4/5

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

Schema description coverage is 0% and there are three required parameters, so the description must carry the load. It does map them collectively — 'tooth counts' for driver and driven, 'drive rpm' for the speed input — and implies the rpm applies to the driver. What it omits is any statement of output units or which tooth count conventionally feeds the numerator, so the mapping is clear but not fully disambiguated.

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 definition opens with a specific verb and resource ('Calculate speed ratio and output speed of one external mesh') and names the exact inputs ('tooth counts and drive rpm'). 'External mesh' scopes it away from internal, bevel, or belt-drive siblings such as bpj_eng_belt_speed, so it is distinguishable without opening any schema.

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?

The phrase 'one external mesh' implicitly limits the tool to a single external gear pair, which is useful scoping context. However, there is no explicit when-to-use/when-not statement and no pointer to what to use for other mesh types (internal, planetary, multi-stage), leaving the agent to infer the boundary.

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.