Skip to main content
Glama

Part-filled horizontal tank

bpj_geom_horizontal_tank
Read-onlyIdempotent

Calculate liquid volume in a level, flat-ended cylindrical tank at a specified fill depth.

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": {
      "radius": "<radius>",
      "length": "<length>",
      "fill": "<fill>"
    },
    "name": "bpj_geom_horizontal_tank"
  }
}

Input Schema

NameRequiredDescriptionDefault
fillYes
lengthYes
radiusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description confirms it is a pure geometric calculation but adds nothing beyond that — no statement of assumed units on the result, no handling of out-of-range fill, no note that the tank is assumed perfectly level.

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 sentence with no filler, and the discriminating qualifiers (level, flat-ended, fill depth) are front-loaded before the object of the calculation.

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 pure calculator with annotations and no output schema, the essentials are present, but key behavioral edges — output unit, treatment of fill above the tank diameter, and confirmation that end caps are ignored — are unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is reported as 0%, but the property titles themselves carry unit and meaning ("Fill depth (m)", "Cylinder length (m)", "Radius (m)"), and the description reinforces the fill-depth concept and the horizontal orientation that makes fill the vertical depth rather than a length coordinate. The remaining gap is the geometric constraint that fill cannot exceed 2×radius; that relationship is left for the agent to infer.

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?

Specific verb plus resource ("Calculate liquid volume in a ... cylindrical tank") with differentiating qualifiers — level, flat-ended, part-filled at a specified fill depth. This separates it from the plain full-cylinder sibling, though it never names an alternative outright.

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?

Usage is only implied: "level, flat-ended" and "at a specified fill depth" silently exclude tilted tanks, domed/spherical ends, and full-cylinder calculations, but the description never states when to use this instead of bpj_geom_cylinder or bpj_geom_pipe_shell, nor any prerequisites.

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.