Skip to main content
Glama

Hollow pipe material volume

bpj_geom_pipe_shell
Read-onlyIdempotent

Calculate material volume and internal space of a cylindrical pipe from its two radii and length.

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": {
      "outerRadius": "<outerRadius>",
      "innerRadius": "<innerRadius>",
      "length": "<length>"
    },
    "name": "bpj_geom_pipe_shell"
  }
}

Input Schema

NameRequiredDescriptionDefault
lengthYes
innerRadiusYes
outerRadiusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/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 safety behavior needs no restating. The description does add real information beyond them by naming the two outputs (material volume and internal space), which matters since there is no output schema. It says nothing about units of results or validation behavior when innerRadius equals or exceeds outerRadius.

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 well-formed sentence with the verb and quantities front-loaded and no filler. It is efficient, though the terseness leaves the gaps above unaddressed rather than earning its brevity through completeness.

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 arithmetic tool with annotations present and no output schema, the definition covers what is computed from what. It is incomplete on the relationship between the radii, on result units, and on the meaning of 'internal space' (inner cylinder volume), which are the details an agent would need to call it confidently.

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?

Schema description coverage is 0%: the parameters carry only titles with units, no descriptions. The description names 'two radii and length' but does not distinguish outer from inner, does not state the innerRadius < outerRadius constraint, and adds nothing about valid ranges beyond what the schema already encodes.

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 gives a specific verb ('Calculate') and specific resources ('material volume and internal space') for a cylindrical pipe, with the input basis stated ('two radii and length'). It does not differentiate itself from related siblings such as bpj_geom_cylinder (solid) or bpj_geom_annulus, which is the main clarity gap.

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?

There is no when-to-use guidance, no mention of when a solid-cylinder tool would be the better choice, and no stated preconditions. The agent must infer the hollow-pipe use case entirely from the phrase 'cylindrical pipe' and the presence of two radii.

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.