Skip to main content
Glama

Spherical cap dimensions

bpj_geom_spherical_cap
Read-onlyIdempotent

Compute curved area, base radius, and volume from sphere radius and cap 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": {
      "radius": "<radius>",
      "cap": "<cap>"
    },
    "name": "bpj_geom_spherical_cap"
  }
}

Input Schema

NameRequiredDescriptionDefault
capYes
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 readOnlyHint, idempotentHint and non-destructive behavior, so the safety profile is covered. The description's added value is naming the three returned quantities even though no output schema exists, but it says nothing about units on the outputs or validity constraints (e.g. cap height relative to radius).

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 front-loaded sentence with the outputs listed before the inputs and 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-math tool with no output schema, naming the three computed quantities is the essential disclosure, and it is present. Minor gaps remain: output units (m², m³) and edge-case behavior for degenerate cap heights are not mentioned.

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%, but the schema titles carry the meaning and units ('Radius (m)', 'Cap height (m)') and both parameters are required. The description restates the two inputs ('sphere radius and cap height') but adds no constraints, relationships, or units beyond what the schema already provides.

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 enumerates the exact outputs (curved area, base radius, volume) plus the two inputs, which separates it from a plain sphere or cone tool in the sibling list. It never names a sibling explicitly, so differentiation is inferred rather than stated.

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?

The description makes the usage context clear (partial-sphere geometry from radius and cap height), but gives no when/when-not rules and no pointer to alternatives such as bpj_geom_sphere for a full sphere. Guidance is implied by the geometry, not stated.

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.