Skip to main content
Glama

Ring torus geometry

bpj_geom_ring_torus
Read-onlyIdempotent

Calculate solid volume and exterior area of a ring torus from its major and tube radii.

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": {
      "major": "<major>",
      "tube": "<tube>"
    },
    "name": "bpj_geom_ring_torus"
  }
}

Input Schema

NameRequiredDescriptionDefault
tubeYes
majorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered. The description adds only that two result quantities are produced; it says nothing beyond that about return shape, units of the outputs, or the formula used. With annotations doing the heavy lifting, this is a modest but non-harmful contribution.

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 front-loads the outputs and closes with the inputs, with zero redundant wording. Nothing could be removed without losing information.

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 pure calculator with annotations covering safety and no output schema, the description states what is computed and from which inputs, which is nearly everything an agent needs. The remaining minor gap is that the return format (two separate values vs. an object) and output units are not stated.

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 parameter meaning: it does identify both inputs as the major radius and tube radius and assigns their roles in the torus geometry. However, it omits any mention of the numeric bounds (1e-9 to 1e9) and whether the two radii are independent or constrained relative to each other, so it only partially compensates for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (calculate) and resource (ring torus) plus the exact outputs (solid volume and exterior area), which clearly separates it from siblings like bpj_geom_sphere, bpj_geom_cylinder, or bpj_geom_pipe_shell. An agent can identify the shape and requested quantities without opening the schema.

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: the tool computes torus properties, so an agent infers when to pick it, but there is no explicit guidance on alternatives (e.g., when a pipe shell or cylinder is the better model) and no stated preconditions. For a self-contained geometry calculator this is adequate, but no exclusions are offered.

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.