Skip to main content
Glama

Truncated cone capacity

bpj_geom_conical_frustum
Read-onlyIdempotent

Find the capacity and lateral surface area of a conical frustum from its end radii and height.

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>",
      "height": "<height>"
    },
    "name": "bpj_geom_conical_frustum"
  }
}

Input Schema

NameRequiredDescriptionDefault
heightYes
innerRadiusYes
outerRadiusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior, so safety is covered. The description adds what the computation produces (capacity plus lateral surface area), but says nothing about output units, whether 'capacity' means volume, or any formula assumptions.

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 that leads with the action and result and immediately states the inputs. There is no filler or redundant restatement of the name.

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 simple three-parameter pure calculation with full annotations, naming both return quantities is adequate. It falls short of complete because output units and the exact meaning of 'capacity' are unstated and there is no output schema to fill the gap.

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%, so the description must carry meaning, and it does map 'end radii' and 'height' to the three required inputs. However, it does not clarify which of outerRadius/innerRadius corresponds to the top versus bottom end, nor does it restate the perpendicular-height constraint or the positive-value bounds that the schema titles encode.

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 names a specific verb ('Find'), a specific shape ('conical frustum'), and the two quantities returned (capacity and lateral surface area), plus the inputs needed (end radii and height). This clearly separates it from the plain-cone sibling bpj_geom_cone, though it never names that sibling explicitly.

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 or when-not-to-use guidance, no stated prerequisites, and no pointer to alternatives such as bpj_geom_cone for a full cone. The agent must infer from the shape name alone whether this is the right tool.

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.