Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_triangular_prism

Calculate triangular prism volume, base area, lateral wall area, and total surface area from triangular base dimensions and prism length, avoiding manual formula and arithmetic errors.

Instructions

Triangular Prism Volume & Surface Area Calculator. Calculate triangular prism volume, lateral face area, base area, and total surface area from triangular base dimensions and prism length. Discipline: GEOMETRY. Governing mathematical model / formula: Volume = Base Area · Length | Total Area = 2 · Base Area + (a + b + c) · Length.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of prism_volume (Prism Volume), base_face_area (Single Triangle Base Area), lateral_surface (Lateral Rectangular Wall Area), total_surface (Total Surface Area (Walls + Ends)) using base_width (Triangular Base Width (b) in units), base_height (Triangular Base Height (h) in units), prism_length (Prism Length (L) 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 'Triangular Prism 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): "triangular-prism"

    • category (string): "geometry"

    • name (string): "Triangular Prism 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.prism_volume (Prism Volume): Formatted display string (e.g. '360.0000 units³')

      • metrics.base_face_area (Single Triangle Base Area): Formatted display string (e.g. '24.0000 units²')

      • metrics.lateral_surface (Lateral Rectangular Wall Area): Formatted display string (e.g. '336.0000 units²')

      • metrics.total_surface (Total Surface Area (Walls + Ends)): Formatted display string (e.g. '384.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_triangular_prism"
  }
}

Input Schema

NameRequiredDescriptionDefault
base_widthNoTriangular Base Width (b) (units). Base edge of triangular face. Default: 8. Min: 0.5. Max: 1000.
base_heightNoTriangular Base Height (h) (units). Perpendicular height of triangular face. Default: 6. Min: 0.5. Max: 1000.
prism_lengthNoPrism Length (L) (units). Extrusion length of prism. Default: 15. Min: 0.5. 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 provided, the description fully carries the behavioral disclosure burden. It states that the tool is pure deterministic computation, read-only, idempotent, stateless, and without side effects, and it explains input validation behavior including safe diagnostic errors for out-of-bounds inputs.

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 structured and front-loaded with purpose, usage, behavior, and returns, making it easy to scan. It is somewhat verbose, especially in the detailed return-value enumeration, but the length is largely justified by the absence of an 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?

Even though no output schema exists, the description fully explains the structured JSON return shape, including status, formula, inputs, metrics, and execution time. Combined with the complete input schema, this is sufficient for an agent to call the tool and interpret its results correctly.

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 input schema already documents base_width, base_height, and prism_length with units, defaults, and bounds. The description reinforces their roles and the governing formula, but it does not add substantial meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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 states a specific verb and resource: calculating triangular prism volume, lateral face area, base area, and total surface area from base dimensions and prism length. It also names the generic dispatcher omni_universal_query as a sibling, so an agent can distinguish this specialist calculator from broader alternatives.

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?

The USAGE GUIDELINES section explicitly states when to use the tool, when not to use it, and routes cross-discipline dynamic dispatch to omni_universal_query. It also specifies the exact input parameters that drive the calculation, leaving little ambiguity about invocation conditions.

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