Skip to main content
Glama

Rotating shaft power

bpj_eng_rotating_shaft_power
Read-onlyIdempotent

Compute angular velocity and shaft power from rotational speed and torque.

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": {
      "torque": "<torque>",
      "rpm": "<rpm>"
    },
    "name": "bpj_eng_rotating_shaft_power"
  }
}

Input Schema

NameRequiredDescriptionDefault
rpmYes
torqueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds that two derived quantities are produced (angular velocity and power), which goes beyond annotations, but it says nothing about the underlying formulas, unit conventions for the outputs, or behavior at extreme inputs despite the schema allowing values from 1e-9 to 1e9.

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, restatement of the title, or redundant phrasing. Nothing in it fails to earn its place.

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?

With no output schema, the description is the only place return values could be characterized, and it names the outputs but not their units (presumably rad/s and W) or sign conventions. For a simple two-parameter physics calculator this is acceptable minimum viability, but it leaves the agent to guess output formatting.

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

Parameters2/5

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

Schema description coverage is 0% — the schema supplies only titles and min/max bounds, no semantic descriptions. The description partially compensates by mapping 'rotational speed' to rpm and 'torque' to torque, but adds no unit clarification for the outputs, no note that rpm must be positive, and no formula linking the two inputs to the two outputs.

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?

The description names a specific verb and resource pair — computing angular velocity and shaft power from rotational speed and torque — so an agent knows exactly what the tool returns. It does not, however, distinguish itself from siblings such as bpj_eng_pump_shaft_input or bpj_eng_belt_speed, which also involve shaft/rotational quantities.

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?

There is no when-to-use guidance, no statement of prerequisites, and no routing to or away from any alternative tool. The agent must infer the use case (rotating machinery power analysis) entirely from the inputs.

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.