Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_regular_polygon

Calculate area, perimeter, apothem, and circumradius for regular polygons with 3 to 1000 sides using side count and length, preventing manual arithmetic and formula errors.

Instructions

Universal Regular N-Sided Polygon Solver (3 to 1000 Sides). Arbitrary n-sided regular polygon solver calculating apothem, circumradius, area, perimeter, and internal angles. Discipline: GEOMETRY. Governing mathematical model / formula: Area = ½ · n · a · r_i | r_i = a / [2 · tan(π/n)] | R = a / [2 · sin(π/n)].

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of area (Polygon Area), perimeter (Perimeter), apothem (Apothem (Inradius r_i)), circumradius (Circumradius (R)) using n (Number of Sides (n) in sides), side (Side Length (a) in units). Guarantees exact machine floating-point precision, eliminating LLM arithmetic mistakes and formula hallucinations.

  • WHEN NOT TO USE: Do not use for qualitative evaluations or unquantified reasoning. All input parameters must be valid numerical values.

  • SIBLING ROUTING: Use this dedicated specialist tool for 'Universal Regular N-Sided Polygon Solver (3 to 1000 Sides)' rather than generic dispatchers like omni_universal_query. For cross-discipline dynamic dispatch, see omni_universal_query.

BEHAVIOR & SAFETY:

  • Pure deterministic computation with machine floating-point precision.

  • Read-only, idempotent, and stateless. Zero side effects or persistent state mutations.

  • Input validation: All arguments are validated against physical and domain bounds. Out-of-bounds inputs return a safe diagnostic error status without throwing runtime exceptions.

RETURNS:

  • Structured JSON object containing:

    • status (string): "success" on valid execution or "error" if validation fails

    • calculator (string): "regular-polygon"

    • category (string): "geometry"

    • name (string): "Universal Regular N-Sided Polygon Solver (3 to 1000 Sides)"

    • formula (string): Governing mathematical formula string

    • inputs (object): Echoed input parameter dictionary with applied defaults

    • metrics (object): Dictionary of computed outputs:

      • metrics.area (Polygon Area): Formatted display string (e.g. '482.8427 sq units')

      • metrics.perimeter (Perimeter): Formatted display string (e.g. '80.0000 units')

      • metrics.apothem (Apothem (Inradius r_i)): Formatted display string (e.g. '12.0711 units')

      • metrics.circumradius (Circumradius (R)): Formatted display string (e.g. '13.0656 units')

    • execution_time_ms (number): Latency in milliseconds.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "omni_regular_polygon"
  }
}

Input Schema

NameRequiredDescriptionDefault
nNoNumber of Sides (n) (sides). Number of polygon vertices. Default: 8. Min: 3. Max: 1000.
sideNoSide Length (a) (units). Outer edge length. Default: 10. Min: 0.001. Max: 100000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full behavioral burden and does so: read-only, idempotent, stateless, zero side effects, deterministic floating-point precision, and bounded input validation that returns a safe diagnostic error instead of raising exceptions. That is precisely the mutation/safety/error context an agent needs before calling.

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

Conciseness4/5

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

Front-loaded with the purpose, then cleanly sectioned into usage, behavior, and returns. It is longer than strictly necessary — the 'eliminating LLM arithmetic mistakes and formula hallucinations' justification and repeated name echoes are filler — but no section is disorganized or redundant enough to impede selection.

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, no-output-schema calculator the description is thorough: it documents the full return shape, status/error semantics, and validation bounds. The only completeness defect is the advertised 'internal angles' output that the RETURNS block omits, a small but real inconsistency.

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 coverage is 100%, so the schema already documents both parameters with types, defaults, and min/max bounds. The description only echoes the parameter names inside the usage prose and supplies the geometric formula relating n and a to the outputs, which adds contextual understanding but no new per-parameter semantics.

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 a specific resource and verb ('n-sided regular polygon solver calculating apothem, circumradius, area, perimeter'). It is unmistakably a geometry calculator, though it never disambiguates from the near-identical sibling omni_regular_polygon_solver, and it advertises 'internal angles' while the RETURNS block lists no angle metric.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit WHEN TO USE / WHEN NOT TO USE / SIBLING ROUTING sections plus a formula-based rationale. However, the when-not block is generic boilerplate ('do not use for qualitative evaluations'), and routing points only at omni_universal_query while ignoring the obvious sibling omni_regular_polygon_solver, leaving a real ambiguity unresolved.

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

Deploy Server

Other Tools