Skip to main content
Glama

Hydrostatic pressure difference

bpj_eng_hydrostatic_head
Read-onlyIdempotent

Calculate pressure rise with depth in a resting fluid from density and standard gravity.

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

Input Schema

NameRequiredDescriptionDefault
headYes
densityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. Beyond that, the description adds real context: gravity is fixed at standard value, the fluid is at rest, and the result is a pressure RISE (a difference, not absolute pressure). It doesn't state that output is in Pa, but the key assumptions are disclosed.

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 gives the operation, the physical model, and the input basis with no wasted words.

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

Completeness4/5

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

For a two-parameter closed-form calculator with full annotations and no output schema, this covers the essentials: inputs, assumed gravity, and the statics assumption. Only the output unit/quantity (pressure difference in Pa) is left implicit.

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 supply units (m for head, kg/m3 for density) and bounds. The description confirms density and gravity are the inputs and recasts 'head' as depth, but does not explain the distinction between head and depth or how to supply values, so it only partially compensates.

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 and physical result: 'Calculate pressure rise with depth in a resting fluid' from density and standard gravity. An agent can tell this is a hydrostatic delta-pressure calculator. It does not name or distinguish itself from any sibling, but the purpose itself is unambiguous.

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 qualifier 'resting fluid' implicitly excludes flowing-fluid problems (e.g. Darcy head loss or pipe flow speed), which is a useful usage boundary. However, there is no explicit when-to-use/when-not-to-use statement and no pointer to related calculators such as unit conversion for pressure.

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.