Skip to main content
Glama

Lead screw travel

bpj_eng_lead_screw_travel
Read-onlyIdempotent

Calculate steady axial feed and travel from screw lead, rotation rate, and run time.

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": {
      "lead": "<lead>",
      "rpm": "<rpm>",
      "time": "<time>"
    },
    "name": "bpj_eng_lead_screw_travel"
  }
}

Input Schema

NameRequiredDescriptionDefault
rpmYes
leadYes
timeYes

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 readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered structurally. The description adds the 'steady' assumption, which is real behavioral context, but says nothing about what values are returned (feed rate vs. distance) or their units, and there is no output schema to fill that gap.

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

Conciseness4/5

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

One front-loaded sentence naming the verb, the outputs, and the inputs with zero filler. It is efficient, though the terseness leaves the aforementioned gaps unaddressed.

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 simple three-parameter deterministic formula with no output schema, the description should state what is returned and in what units (e.g. feed in mm/min, travel in mm). It names the outputs conceptually but leaves their units and the relationship between them 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 0%, so the description carries the burden, but it merely restates the three inputs already titled in the schema ('Lead (mm/rev)', 'Shaft speed (rpm)', 'Run time (s)'). It does not clarify unit expectations, sign conventions, or how lead relates to the resulting feed, so it adds little meaning beyond the schema titles.

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 (calculate) and specific outputs (steady axial feed and travel) derived from named inputs (screw lead, rotation rate, run time). The resource is unambiguous and does not overlap with siblings like bpj_eng_belt_speed or bpj_eng_wheel_rollout, though the description never explicitly differentiates itself from 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 word 'steady' implies the tool assumes constant rotation and no acceleration ramp, which is an implicit usage condition. There is no explicit when-to-use guidance, no note about when this model is inappropriate (e.g. accelerating or reversing screws), and no named alternatives.

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.