Scientific Calculator

Regular Polygon Calculator

calculator_polygon

Read-only

Regular polygon perimeter, area, interior angle, sum of interiors, apothem. n_sides >= 3.

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": {
      "n_sides": "<n_sides>"
    },
    "name": "calculator_polygon"
  }
}

Input Schema

Name	Required	Description	Default
`apothem`	No	Known apothem.
`n_sides`	Yes	Number of sides (>=3).
`perimeter`	No	Known perimeter.
`calculation`	No	perimeter\|area\|interior_angle\|sum_interior_angles\|apothem\|side_length\|all	all
`side_length`	No	Side length.

Output Schema

Name	Required	Description	Default
`result`	No
`n_sides`	Yes
`expression`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds only the domain constraint (n_sides >= 3), which is also in the schema, and says nothing about which inputs drive a computation or what happens with insufficient given values.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two fragments, no wasted words, and the constraint is placed last where it is visible. However the telegraphic noun-list style omits a leading verb, making it read more like a schema echo than an instruction.

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?

With an output schema present and full parameter coverage, the remaining burden is usage guidance and the interaction between the three 'known value' parameters, neither of which the description addresses. Adequate for a simple read-only calculator but with clear gaps.

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 100%, so each of the five parameters is already documented with type, examples, and meaning. The description restates the n_sides >= 3 bound but adds no explanation of how side_length/apothem/perimeter interact as alternative givens.

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?

The description names the resource (regular polygon) and enumerates the quantities computed (perimeter, area, interior angle, sum of interiors, apothem). It implicitly differentiates from calculator_triangle/square/rectangle by being the general n-sided form, though it does not name those siblings.

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?

There is no statement of when to use this tool versus the many other geometry calculators, nor any prerequisites beyond the bare 'n_sides >= 3' constraint. The agent must infer usage from the tool name and output list.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Scientific Calculator tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.