Skip to main content
Glama
tresor4k

macalc

calculate_water_pressure_loss

Calculate water pressure loss in a pipe circuit accounting for friction and elevation. Input pipe length, diameter, flow rate, elevation change, and fittings to get equivalent length for pipe sizing or pump selection.

Instructions

Calculate water pressure loss in a pipe circuit including friction and elevation. Returns: {equiv_length_m}. See list_bundles for related 'plomberie' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pipe_length_mYesPipe length in meters
diameter_mmYesPipe internal diameter in millimeters
flow_rate_lpmYesFlow rate in liters per minute
elevation_change_mNoElevation change in meters (positive = uphill, negative = downhill)
fittings_countNoNumber of fittings and elbows (each adds ~0.5m equivalent length)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoComputed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools).
formulaNoHuman-readable formula or method used (e.g. "I=P·r·t", "Magnus formula").
sourceNoAuthoritative source for the rule or formula (e.g. "Article 197 CGI", "NF DTU 21").
reference_urlNoLink to a calcul2 page documenting the calculation in detail.
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only states that friction and elevation are included and returns {equiv_length_m}, omitting details like assumptions, determinism, or limitations. Lacks depth for a calculation tool.

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?

Two sentences, no superfluous words. Front-loaded with the purpose, followed by output hint and a useful pointer to related tools. Highly efficient.

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?

Adequate given the existence of output schema and rich input schema, but lacks explanation of calculation method (e.g., formula used) and potential assumptions, which are important for a hydraulic tool.

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 coverage is 100% with each parameter well-described. The description does not add meaning beyond the schema, meeting the baseline but not exceeding it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states the tool calculates water pressure loss in a pipe circuit including friction and elevation. It uses a specific verb ('Calculate') and resource ('water pressure loss'), clearly distinguishing it from sibling tools like calculate_pipe_diameter.

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 provides no guidance on when to use this tool versus alternatives. The mention of 'See list_bundles' is a weak reference but does not explicitly state conditions or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tresor4k/macalc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server