Skip to main content
Glama

Stadium outline

bpj_geom_stadium
Read-onlyIdempotent

Calculate the area and perimeter of two semicircles joined by parallel straight sides.

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": {
      "straight": "<straight>",
      "radius": "<radius>"
    },
    "name": "bpj_geom_stadium"
  }
}

Input Schema

NameRequiredDescriptionDefault
radiusYes
straightYes

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 establish that this is a read-only, idempotent, non-destructive, closed-world calculation, so the safety profile is covered. The description adds that it computes two outputs (area and perimeter), but it does not state return format, precision, rounding, or output units; with no output schema that detail is absent.

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?

Single front-loaded sentence with no filler or redundancy. It states the computed quantities and shape in one pass.

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 two-parameter geometry calculator, the definition covers the shape and the two computed quantities, and annotations cover safety. However, with no output schema it does not specify output units or result structure, leaving a gap for correct downstream use.

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 must carry parameter meaning. It only implies that 'radius' belongs to the semicircles and 'straight' is a parallel side; it never names the parameters, clarifies that 'straight' is the length of one straight side, or restates the meter units. The schema property titles help, but the description does not compensate for the low coverage.

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 the exact geometric resource and outputs ('area and perimeter of two semicircles joined by parallel straight sides'). The shape definition is distinctive enough to separate it from sibling calculators such as ellipse or annulus.

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: an agent can infer it should be called when it needs the area or perimeter of a stadium shape. There is no explicit when-to-use guidance, no mention of alternatives, and no exclusions or prerequisites.

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.