Skip to main content
Glama

Wheel rollout distance

bpj_eng_wheel_rollout
Read-onlyIdempotent

Estimate ground distance from measured rolling diameter and counted turns without slip.

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": {
      "diameter": "<diameter>",
      "turns": "<turns>"
    },
    "name": "bpj_eng_wheel_rollout"
  }
}

Input Schema

NameRequiredDescriptionDefault
turnsYes
diameterYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds the meaningful modeling assumption of no slip, but omits other behavioral context such as the underlying relation (circumference x turns) and expected output units.

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 zero filler; the inputs and the key constraint appear immediately. Nothing is redundant with the title or schema.

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?

For a two-parameter calculator with no output schema, the essential inputs are identified, but the description never states the output (ground distance) unit or the formula assumption beyond 'no slip'. Diameter is given in mm, yet whether the returned distance is mm or meters is unstated.

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 0%, so the description must carry parameter meaning; it partially does by clarifying that diameter is the 'rolling'/effective diameter (not nominal) and turns are the counted revolutions. It still does not state how the two combine or what unit the result carries, leaving real ambiguity.

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?

States a specific verb ('Estimate') and resource ('ground distance'), plus the two inputs that produce it (rolling diameter, counted turns). It is distinguishable from siblings like bpj_eng_lead_screw_travel or bpj_eng_belt_speed by the rolling-diameter framing, though it does not explicitly contrast with them.

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 'without slip' implies the applicability condition (ideal rolling contact, no wheelspin), which is useful usage guidance. However, there is no explicit when-to-use/when-not-to-use statement and no pointer to related kinematic siblings.

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.