Skip to main content
Glama

Mean speed in a pipe

bpj_eng_pipe_flow_speed
Read-onlyIdempotent

Calculate the cross-section and mean flow speed of a full circular pipe.

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": {
      "flow": "<flow>",
      "diameter": "<diameter>"
    },
    "name": "bpj_eng_pipe_flow_speed"
  }
}

Input Schema

NameRequiredDescriptionDefault
flowYes
diameterYes

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 readOnly, idempotent, non-destructive, and closed-world behavior. The description adds the important 'full circular pipe' assumption, but it omits the formula, output units, and any failure conditions or limitations.

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?

The definition is a single front-loaded sentence with no redundant restatement of the tool name or title. It is appropriately sized for a simple two-parameter calculation tool.

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 calculator this is close to adequate, but there is no output schema and the description does not specify output units or the calculation relationship. Input units appear only in schema titles, leaving the definition somewhat incomplete for engineering use.

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?

With 0% schema description coverage, the description must compensate by explaining the two required parameters, but it never names flow or diameter, their units, or how they combine. The parameter titles in the schema carry the units, so the description adds little semantic value beyond them.

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 states a specific verb and resource: calculate cross-section and mean flow speed for a full circular pipe. It is clear about what the tool computes, but it does not differentiate this from sibling pipe/flow calculation tools.

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 phrase 'full circular pipe' implies the applicable condition, but there is no explicit when-to-use or when-not-to-use guidance. It also does not name alternatives such as Reynolds pipe calculations or volume-flow unit conversions.

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.