Skip to main content
Glama

Straight pipe friction loss

bpj_eng_darcy_head_loss
Read-onlyIdempotent

Estimate straight-pipe head loss with the Darcy friction factor and Darcy–Weisbach equation.

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": {
      "factor": "<factor>",
      "length": "<length>",
      "diameter": "<diameter>",
      "speed": "<speed>"
    },
    "name": "bpj_eng_darcy_head_loss"
  }
}

Input Schema

NameRequiredDescriptionDefault
speedYes
factorYes
lengthYes
diameterYes

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 readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds the meaningful scoping detail that this is straight-pipe friction loss only (no minor/fitting losses) and that it is a Darcy–Weisbach estimate, but it omits the return units, the gravity constant assumed, and any accuracy caveats.

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?

A single, front-loaded sentence with zero filler and the computing method placed immediately after the purpose. It is efficient, though the terseness comes at the cost of the missing usage and output detail scored elsewhere.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With four required parameters, no output schema, and no parameter descriptions, the definition should state what is returned and in what units (head in meters of fluid?) and note that f must be supplied externally. Neither is present, leaving a real gap for a physics calculator with no output schema.

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%, though parameter titles carry names and SI units (m/s, m, m). The description's only added semantic is the crucial qualifier that 'factor' is the Darcy (not Fanning) friction factor, a 4x-relevant distinction; it says nothing about 'speed' being mean velocity or about the diameter convention beyond the title.

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?

Names a specific verb ('Estimate'), a specific quantity ('straight-pipe head loss'), and the method (Darcy friction factor / Darcy–Weisbach). This is clearly distinguishable from siblings like pipe_flow_speed or reynolds_pipe, but it never explicitly contrasts itself with them, so it sits at clear-but-undifferentiated.

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?

No when-to-use, when-not-to-use, or prerequisite guidance. The requirement for a pre-known Darcy friction factor implies the user must obtain f elsewhere (e.g., via a Reynolds/Colebrook step), but the description never says this or points to a sibling for computing f.

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.