Skip to main content
Glama

Regular polygon dimensions

bpj_geom_regular_polygon
Read-onlyIdempotent

Calculate apothem, circumradius, and area from a regular polygon’s side count and length.

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": {
      "sides": "<sides>",
      "side": "<side>"
    },
    "name": "bpj_geom_regular_polygon"
  }
}

Input Schema

NameRequiredDescriptionDefault
sideYes
sidesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds little beyond that—no statement about precision, unit handling, or what happens with degenerate inputs. For a simple annotated calculator this is acceptable but not generous.

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 naming inputs first and outputs second, with no filler or redundant restatement of the title. Every clause earns its place.

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?

With no output schema, the description does the necessary work of enumerating the three returned values, which is the key completeness requirement here. Remaining gaps (units of the side length, bounds on side count) are minor for a stateless read-only calculator.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 meaning, and it does map both inputs ('side count and length') to the two required parameters while implying the result values. It stops short of stating units or the minimum of 3 sides enforced by the schema, so it only partly compensates.

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 (regular polygon) plus exactly which derived quantities it returns: apothem, circumradius, and area. That output list distinguishes it from the many sibling geometry calculators (rhombus, trapezoid, circular_sector) that compute different property sets.

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 applies when a regular polygon's side count and length are known and derived radii/area are needed. There is no explicit when-not guidance, no mention of alternative tools for irregular polygons, and no note that this is a pure computation with no state.

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.