Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_torus

Calculate torus volume, surface area, inner hole diameter, and outer diameter from major and minor radii for exact geometry results.

Instructions

Torus Volume & Surface Area (Donut) Calculator. Calculate donut torus volume and surface area using Pappus's Centroid Theorems from major radius R and minor radius r. Discipline: GEOMETRY. Governing mathematical model / formula: Volume = 2π² · R · r² | Surface Area = 4π² · R · r.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of torus_volume (Torus Volume), torus_surface_area (Total Surface Area), hole_diameter (Inner Hole Diameter (2(R - r))), outer_diameter (Outer Outer Diameter (2(R + r))) using major_radius (Major Radius (R) in units), minor_radius (Minor Radius (r) 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 'Torus Volume & Surface Area (Donut) Calculator' 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): "torus"

    • category (string): "geometry"

    • name (string): "Torus Volume & Surface Area (Donut) Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.torus_volume (Torus Volume): Formatted display string (e.g. '1,776.5288 units³')

      • metrics.torus_surface_area (Total Surface Area): Formatted display string (e.g. '1,184.3525 units²')

      • metrics.hole_diameter (Inner Hole Diameter (2(R - r))): Formatted display string (e.g. '14.0000 units')

      • metrics.outer_diameter (Outer Outer Diameter (2(R + r))): Formatted display string (e.g. '26.0000 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_torus"
  }
}

Input Schema

NameRequiredDescriptionDefault
major_radiusNoMajor Radius (R) (units). Distance from center of hole to center of tube (R > r). Default: 10. Min: 1. Max: 1000.
minor_radiusNoMinor Radius (r) (units). Radius of the revolving tube cross-section. Default: 3. Min: 0.1. Max: 500.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.8/5.0
Behavior5/5

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

No annotations are supplied, so the description carries the full burden and does: deterministic read-only, idempotent, stateless, zero side effects, bound-validated inputs that return a diagnostic error status rather than throwing. It also documents the full response envelope (status, calculator, category, formula, inputs, metrics, execution_time_ms).

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?

Well front-loaded with labeled sections (usage, behavior, returns) and no filler sentences; the formula line up front is genuinely useful. It is somewhat long, with the metric names and descriptions restated in both the WHEN TO USE list and the RETURNS block, which is mild redundancy rather than noise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Only two optional numeric parameters and no output schema, yet the description fully specifies inputs, defaults, constraints, failure mode, and the exact shape of the returned JSON including example formatted values. An agent could call and parse this correctly with no further information.

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 coverage is already 100%, so the baseline is 3; the description earns above that by adding the geometric constraint R > r and the physical meaning of each radius ('distance from center of hole to center of tube', 'radius of the revolving tube cross-section'), plus the derived formulas. It does not add unit-conversion or edge-case guidance beyond the bounds already in the schema.

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 and resource ('Calculate donut torus volume and surface area using Pappus's Centroid Theorems from major radius R and minor radius r') and enumerates the four outputs, so the agent knows exactly what the tool computes. It also names the generic dispatcher omni_universal_query as the thing it is not, distinguishing it from siblings.

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

Usage Guidelines5/5

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

Explicit WHEN TO USE with the precise output keys, an explicit WHEN NOT TO USE ('qualitative evaluations or unquantified reasoning', all inputs must be numeric), and explicit SIBLING ROUTING to omni_universal_query for cross-discipline dispatch. Nothing about invocation conditions is left to inference.

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