Skip to main content
Glama

Pipe Reynolds number

bpj_eng_reynolds_pipe
Read-onlyIdempotent

Calculate dimensionless Reynolds number from mean velocity, inside diameter, and kinematic viscosity.

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": {
      "speed": "<speed>",
      "diameter": "<diameter>",
      "viscosity": "<viscosity>"
    },
    "name": "bpj_eng_reynolds_pipe"
  }
}

Input Schema

NameRequiredDescriptionDefault
speedYes
diameterYes
viscosityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data and the description need not repeat it. Beyond that, the description adds only the fact that the result is 'dimensionless' — a small but real piece of context. It says nothing about unit-consistency assumptions, validity limits of the formula, or what the returned magnitude implies (e.g. laminar vs turbulent thresholds).

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 that names the operation and its three inputs with zero filler or redundancy. Nothing could be removed without losing information.

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 three-parameter, annotation-covered, output-schema-less calculator, the definition is minimally sufficient: the agent knows what goes in and roughly what comes out. It stops short of being fully complete because the unit contract and the characteristic validity of the Reynolds formula are never stated, and there is no routing hint against the many sibling engineering calculators.

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%, but each property carries a title with units ('Mean speed (m/s)', 'Inside diameter (mm)', 'Kinematic viscosity (mm2/s)'), and the description restates all three inputs, so the agent can map values to parameters. However, the description uses 'mean velocity' where the schema says 'Mean speed', and it never mentions the mixed units (m/s velocity against mm and mm2/s), which is the one thing that could cause a caller to pre-convert incorrectly.

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 a well-defined resource ('dimensionless Reynolds number') and enumerates the three physical inputs it consumes. An agent can immediately tell this is a single-formula engineering calculator. It does not, however, distinguish itself from adjacent siblings such as bpj_eng_pipe_flow_speed or bpj_eng_darcy_head_loss, so sibling differentiation is left to the name.

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?

The description gives no when-to-use or when-not-to-use guidance and names no alternative tool. Nothing tells the agent whether to reach for this versus the pipe-flow-speed or Darcy head-loss calculators, nor what preconditions (single-phase flow, Newtonian fluid) apply.

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.