Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_cylinder

Calculate cylinder volume, lateral and total surface area, and base circumference from radius and height to get exact geometry results.

Instructions

Cylinder Volume & Surface Area Calculator. Calculate cylinder volume, lateral curved surface area, total surface area, and base perimeter from radius and height. Discipline: GEOMETRY. Governing mathematical model / formula: Volume = π · r² · h | Total Surface Area = 2πr(r + h).

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of cylinder_volume (Cylinder Volume), lateral_area (Lateral Curved Surface Area), total_surface_area (Total Surface Area (Caps + Body)), base_circumference (Base Perimeter / Circumference) using radius (Cylinder Radius (r) in units), height (Height (h) 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.

DISAMBIGUATION & BOUNDARIES:

  • Use this dedicated specialist tool for 'Cylinder Volume & Surface Area Calculator' rather than generic dispatchers like omni_universal_query.

  • For multi-calculation chained jobs, use 'omni_batch_calculate'.

  • To inspect schema fields, see 'omni_describe_solver'.

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): "cylinder"

    • category (string): "geometry"

    • name (string): "Cylinder 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.cylinder_volume (Cylinder Volume): Formatted display string (e.g. '942.4778 units³')

      • metrics.lateral_area (Lateral Curved Surface Area): Formatted display string (e.g. '376.9911 units²')

      • metrics.total_surface_area (Total Surface Area (Caps + Body)): Formatted display string (e.g. '534.0708 units²')

      • metrics.base_circumference (Base Perimeter / Circumference): Formatted display string (e.g. '31.4159 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_cylinder"
  }
}

Input Schema

NameRequiredDescriptionDefault
heightNoHeight (h) (units). Cylinder altitude. Default: 12. Min: 0.1. Max: 1000.
radiusNoCylinder Radius (r) (units). Radius of circular base. Default: 5. 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?

With no annotations supplied, the description fully carries the behavioral burden: it states deterministic computation, read-only/idempotent/stateless behavior, absence of side effects, input-bound validation, and safe diagnostic errors instead of exceptions.

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 description is front-loaded and organized into purpose, usage, disambiguation, behavior, and returns. It is somewhat long and repetitive in places, but the structure is clear and the returns detail compensates for the missing output schema.

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?

Given the tool's simplicity, absence of annotations, and absence of an output schema, the description supplies complete behavioral and return-value context. An agent has enough information to call it correctly and interpret the structured result.

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 the schema already documents radius and height with units, defaults, and bounds. The description names the parameters but does not add meaning beyond the schema's own parameter documentation.

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 names a specific calculator, states the exact geometric quantities computed, and gives the governing formulas. It clearly distinguishes this specialist tool from generic dispatchers and batch tools.

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 provides explicit WHEN TO USE and WHEN NOT TO USE sections, names alternative sibling tools for generic queries, batch jobs, and schema inspection, and states the numerical input requirement.

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