Skip to main content
Glama

Sphere dimensions

bpj_geom_sphere
Read-onlyIdempotent

Calculate volume, surface area, and great-circle circumference of a sphere.

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

Input Schema

NameRequiredDescriptionDefault
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 readOnly, idempotent, non-destructive, and closed-world, so the safety profile is fully covered elsewhere. The description adds real value by disclosing that three distinct measurements are returned, but says nothing about output units (m, m², m³) or return shape, which is the remaining behavioral gap.

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 zero filler, front-loaded with the action verb and immediately followed by the exact outputs. 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 one-parameter, deterministic calculator with no output schema, the description is nearly sufficient: it names the shape and all three results. The only omission worth flagging is output units and format, which is a small gap given the schema already labels the input in meters.

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?

Only one parameter exists and the schema already supplies its title ('Radius (m)') plus min/max bounds, so the schema carries the semantics. The description adds nothing about how the radius relates to the outputs (e.g., which quantities are linear vs squared vs cubic), leaving it at baseline.

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?

Uses a specific verb ('Calculate') with a precisely named resource ('sphere') and enumerates the three returned quantities: volume, surface area, and great-circle circumference. This separates it cleanly from shape-specific siblings such as bpj_geom_spherical_cap or bpj_geom_circle_segment without needing to name them.

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?

The description provides no when-to-use guidance, no prerequisites, and no mention of how to choose between this and the many other geometry siblings. Usage is only implied by the stated quantities being computable from a radius.

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.