Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_sphere

Calculate exact sphere volume, surface area, diameter, and Archimedean cylinder ratio from a radius to eliminate manual arithmetic and formula errors.

Instructions

Sphere Volume & Surface Area Calculator. Calculate exact sphere volume, surface area, radius, diameter, and circumscribed cylinder ratio using Archimedes' theorem. Discipline: GEOMETRY. Governing mathematical model / formula: Volume = 4/3 · π · r³ | Surface Area = 4 · π · r².

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of sphere_volume (Sphere Volume), surface_area (Surface Area), diameter (Diameter (2r)), cylinder_ratio (Archimedean Cylinder Ratio) using radius (Sphere 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 'Sphere Volume & Surface Area 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): "sphere"

    • category (string): "geometry"

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

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.sphere_volume (Sphere Volume): Formatted display string (e.g. '1,436.7550 units³')

      • metrics.surface_area (Surface Area): Formatted display string (e.g. '615.7522 units²')

      • metrics.diameter (Diameter (2r)): Formatted display string (e.g. '14.0000 units')

      • metrics.cylinder_ratio (Archimedean Cylinder Ratio): Formatted display string (e.g. 'Exact 2:3 Volume Ratio')

    • 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_sphere"
  }
}

Input Schema

NameRequiredDescriptionDefault
radiusNoSphere Radius (r) (units). Distance from center to surface. Default: 7. Min: 0.1. Max: 1000.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.6/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: it declares the tool read-only, idempotent, stateless, side-effect free, deterministic with floating-point precision, and states that out-of-bounds inputs return a diagnostic error status rather than throwing. That covers the safety profile 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?

The definition is front-loaded and sectioned (usage, behavior, returns), with the purpose and formulas appearing first. It is somewhat verbose in the RETURNS block, listing metadata fields like calculator, category, and name that are boilerplate rather than decision-relevant, which costs a point.

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?

For a single-parameter deterministic calculator with no output schema, the description supplies inputs, formulas, validation bounds behavior, error semantics, and a full breakdown of the returned JSON including each metric. Nothing an agent needs to invoke or interpret it is missing.

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% and the sole parameter already documents meaning, default (7), and min/max bounds; the description only restates 'radius (Sphere Radius (r) in units)' without adding format or edge-case nuance beyond the schema. This is the baseline case where the schema does the work.

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?

The description opens with a specific verb-and-resource pair ('Sphere Volume & Surface Area Calculator') and enumerates exactly which quantities are computed (volume, surface area, diameter, cylinder ratio) along with the governing formulas. This is unambiguously distinct from data-lookup or dispatch 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?

It supplies an explicit WHEN TO USE clause naming the outputs and the single input, an explicit WHEN NOT TO USE clause excluding qualitative reasoning and non-numeric inputs, and sibling routing that names omni_universal_query as the generic dispatcher to avoid for this task.

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