Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_octagon_solver

Compute every dimension of a regular octagon from one known value, back-solving side length, area, perimeter, radii, diagonals, and miter cuts for geometry and framing tasks.

Instructions

Regular Octagon 8-Variable Bidirectional Solver: Exact regular octagon dimensional solver resolving side length, area, perimeter, apothem (inradius), circumradius, span across flats, short diagonal, long diagonal, miter saw angle, and corner cutoff using closed-form radical expressions.

Governing formulas:

  • Area = 2 · (1 + √2) · a²

  • Apothem = [a · (1 + √2)] / 2

  • Circumradius = a · √[(1 + √2) · √2 / 2]

  • Span (flat-to-flat) = a · (1 + √2)

  • Short Diagonal = a · √(2 + √2)

  • Long Diagonal = a · √(4 + 2√2)

  • Miter Angle = 22.5° | Corner Cutoff = a / √2

BIDIRECTIONAL DRIVER & VALUE PAIRING:

  • Set 'driver' to the name of the single known reference parameter: 'side', 'area', 'perimeter', 'apothem', 'circumradius', 'span', 'short_diagonal', or 'long_diagonal'.

  • Set 'value' to its positive numerical magnitude (e.g. driver='area', value=482.84).

  • The solver algebraically backsolves all remaining 7 geometric parameters simultaneously.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke whenever solving regular 8-sided polygon geometry, architectural framing, miter cuts, or area conversions from any known dimension. Eliminates LLM floating-point errors on radical roots like √(4 + 2√2).

  • WHEN NOT TO USE: Do not use for irregular octagons, non-planar 3D geometry, or non-8-sided polygons.

  • SIBLING ROUTING: Use omni_octagon_solver specifically for 8-sided regular octagons where closed-form radical representations are required. For arbitrary n-sided regular polygons where n != 8 (e.g. triangles n=3, pentagons n=5, hexagons n=6, decagons n=10, or arbitrary n up to 1000), route to omni_regular_polygon_solver instead.

BEHAVIOR & SAFETY:

  • Pure deterministic geometric computation with machine floating-point precision.

  • Read-only, idempotent, and stateless. Zero side effects or external network mutations.

  • Enforces strict input validation (value > 0). Out-of-bounds inputs return safe diagnostic error.

  • Output floating-point metrics rounded to user-specified precision (between 2 and 14 decimal places, default 6).

RETURNS:

  • Structured JSON object containing:

    • source (string): Canonical documentation URL

    • driver_parameter (string): Echoed driver name

    • driver_value (number): Echoed driver value

    • metrics (object): Calculated dimensional metrics:

      • side_length (number): Outer regular edge length (units)

      • area (number): Total enclosed area (sq units)

      • perimeter (number): Boundary length 8a (units)

      • apothem (number): Center-to-flat inradius (units)

      • circumradius (number): Center-to-vertex radius (units)

      • span_flat_to_flat (number): Width across opposite flat sides (units)

      • short_diagonal (number): Distance between alternate vertices (units)

      • long_diagonal (number): Maximum diameter across opposite vertices (units)

    • exact_closed_forms (object): Symbolic radical mathematical formulas for all quantities

    • miter_angle_deg (number): Exact saw bevel angle (22.5°)

    • corner_cutoff (number): Truncated corner leg length (units)

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": {
      "value": "<value>"
    },
    "name": "omni_octagon_solver"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYesNumerical positive value of the known reference driver parameter (e.g. 10.0).
driverNoThe known reference parameter driving the bidirectional calculation. Pairs with 'value' to instantaneously backsolve all other 7 variables.side
precisionNoDecimal places of precision for output floating-point metrics (integer between 2 and 14, default 6).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.2
    • changedInput schema / properties / driver / description
      Previous value: -"The known reference parameter driving the bidirectional calculation"New value: +"The known reference parameter driving the bidirectional calculation. Pairs with 'value' to instantaneously backsolve all other 7 variables."
    • changedInput schema / properties / precision / description
      Previous value: -"Decimal places of precision (2-14)"New value: +"Decimal places of precision for output floating-point metrics (integer between 2 and 14, default 6)."
    • changedInput schema / properties / value / description
      Previous value: -"Numerical value of the known driver parameter"New value: +"Numerical positive value of the known reference driver parameter (e.g. 10.0)."
  2. First observedv0.1.0

TDQS

Score is being calculated.

Deploy Server

Other Tools