Skip to main content
Glama

Conveyor belt speed

bpj_eng_belt_speed
Read-onlyIdempotent

Estimate no-slip belt travel speed from effective drum diameter and rotation rate.

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>",
      "rpm": "<rpm>"
    },
    "name": "bpj_eng_belt_speed"
  }
}

Input Schema

NameRequiredDescriptionDefault
rpmYes
diameterYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds one useful behavioral qualifier, the no-slip assumption (and "effective" diameter), but says nothing about the computational model, unit conventions of the result, or limits.

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; the assumption and the two inputs come before any detail an agent would need.

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 two-parameter calculation tool with full annotation coverage and no output schema, the definition gives enough to invoke it correctly: what is computed, from what, and under what assumption. The only real gap is the unit of the returned speed, which is minor.

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%, though the schema titles carry units (rpm, mm). The description names both parameters and adds meaning with "effective" diameter, signaling that the wrapped/lagged effective diameter should be used rather than a nominal one. It does not restate units or clarify which diameter convention to pick, so compensation is partial.

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 ("no-slip belt travel speed") with the two governing inputs named, which distinguishes it from siblings such as bpj_eng_lead_screw_travel or bpj_eng_wheel_rollout. It does not explicitly name an alternative, so it sits just below the top band.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use, when-not-to-use, or alternative guidance is given. The only implicit qualifier is the "no-slip" assumption, which hints at applicability but is not framed as guidance for choosing this tool.

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.