Skip to main content
Glama

Annular cross-section

bpj_geom_annulus
Read-onlyIdempotent

Compute material area, radial thickness, and total boundary length of an annulus.

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

Input Schema

NameRequiredDescriptionDefault
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 readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds value by naming the exact outputs, but omits behavioral edges that matter for a calculator: what happens when innerRadius >= outerRadius, and whether results are unit-agnostic. With annotations carrying safety, a 3 reflects modest added context.

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 front-loaded sentence with zero filler; every clause names a concrete computed quantity. It is efficient, though its brevity comes at the cost of the missing guidance noted elsewhere rather than from trimming redundancy.

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 trivial two-parameter readonly geometry calculator with annotations and no output schema, the description is adequate: it tells the agent what will be returned without needing to describe a response object. However, it should still state the radius ordering assumption and unit handling to be fully self-sufficient.

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%, so the description carries the burden of explaining the two numeric inputs, yet it never mentions innerRadius or outerRadius at all. It also fails to state the implied ordering constraint (inner < outer) or the unit convention, leaving only the schema titles ('Inner radius (m)') to convey meaning.

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 ('compute') and resource ('annulus') and enumerates the three derived quantities: material area, radial thickness, and total boundary length. An agent can tell this is a solid-ring geometry calculator, though it never names a sibling such as bpj_geom_pipe_shell or bpj_geom_ring_torus to distinguish the 2D annulus from related shapes.

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, and no mention of the closely related siblings (pipe shell, ring torus, circle segment) that an agent might pick instead. The agent must infer the applicability purely from the tool name and the shape being described.

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.