Skip to main content
Glama

Mean piston speed

bpj_eng_mean_piston_speed
Read-onlyIdempotent

Estimate mean piston travel speed from full stroke and crankshaft rpm using two strokes per revolution.

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": {
      "stroke": "<stroke>",
      "rpm": "<rpm>"
    },
    "name": "bpj_eng_mean_piston_speed"
  }
}

Input Schema

NameRequiredDescriptionDefault
rpmYes
strokeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

The annotations already state read-only, idempotent, closed-world, and non-destructive behavior, so safety is covered. The description adds useful model context (two strokes per revolution) but says nothing about the output's units or scale, which is the main behavioral unknown for an engineering calculation.

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?

One sentence, front-loaded with the computed quantity and then the inputs and formula basis. There is no redundant wording, and nothing that should be moved ahead of the purpose statement.

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 closed-form calculator, almost everything needed to invoke the tool is present, and the annotations cover the safety profile. The notable gap is the output unit of mean piston speed (e.g., m/s vs mm/min), which no output schema exists to clarify.

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%, but only two parameters exist, each with a descriptive title ("Shaft speed (rpm)", "Full stroke (mm)"), so the schema already covers most parameter meaning. The description maps them to their roles (full stroke and crankshaft rpm) and states the two-strokes-per-revolution relation, but it does not specify how stroke and rpm combine into a speed value or what unit results.

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 description states a specific verb ("Estimate") and a precise resource ("mean piston travel speed"), and it also names the inputs and the underlying model (two strokes per revolution). That distinguishes it from the other speed calculators in this group, such as belt_speed and pipe_flow_speed, without requiring the schema to be opened.

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 intended use of the tool is implied by the physics of piston speed, but the description gives no explicit instruction about when to use it and when to prefer a sibling such as belt_speed. Since the other tools compute different quantities, the implicit disambiguation is reasonable, yet nothing here routes the agent explicitly.

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.