Skip to main content
Glama

Pump shaft power estimate

bpj_eng_pump_shaft_input
Read-onlyIdempotent

Estimate hydraulic output and shaft input from fluid head, flow, density, and pump efficiency.

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": {
      "head": "<head>",
      "flow": "<flow>",
      "density": "<density>",
      "efficiency": "<efficiency>"
    },
    "name": "bpj_eng_pump_shaft_input"
  }
}

Input Schema

NameRequiredDescriptionDefault
flowYes
headYes
densityYes
efficiencyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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. The description adds only that two quantities are produced, without disclosing whether efficiency is applied as a divisor, what units the outputs use, or what happens at edge conditions. Useful but thin beyond the annotations.

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 the computed outputs first and the required inputs second; no filler, restatement, or hedging.

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?

The tool is a simple read-only calculation with no output schema, so the description need not detail return structure. However, it promises two outputs (hydraulic output and shaft input) whose units and formatting are never stated, leaving an agent unable to interpret results confidently.

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%, so the description must compensate, and it does name all four parameters and clarify that 'head' means fluid head and 'efficiency' is pump efficiency. It does not add acceptable ranges or explain that efficiency is a percentage in (0,100], which the schema titles alone convey.

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') plus the two computed resources (hydraulic output and shaft input) and the domain (pump). The inputs named (fluid head, flow, density, pump efficiency) distinguish it from the rotational-shaft-power sibling, though the description does not explicitly contrast with that sibling.

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?

Usage is only implied: the agent must infer from the input list that this applies to liquid pumping systems with known head, flow, density, and efficiency. There is no statement of when not to use it, no prerequisite guidance, and no named alternative for adjacent calculations.

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.