Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_gravel

Calculate gravel, crushed stone, or pea gravel tonnage from area length, width, and depth. Returns cubic yards, cubic feet, tons needed, and tandem truckloads for driveways, bases, and drainage.

Instructions

Gravel & Crushed Stone Tonnage Calculator. Calculate cubic yards and metric/US tons of gravel, crush-and-run, or pea gravel for driveways, bases, and drainage. Discipline: CONSTRUCTION. Governing mathematical model / formula: Tons = [Cubic Yards × 1.4 Tons/cu yd].

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of tons_needed (Gravel Required), cubic_yards (Volume (Cubic Yards)), cubic_feet (Volume (Cubic Feet)), tandem_loads (Tandem Dump Truck Loads (~14t)) using length (Driveway / Area Length in ft), width (Driveway / Area Width in ft), depth (Gravel Depth in in), density (Aggregate Density in tons/yd³). 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 'Gravel & Crushed Stone Tonnage 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): "gravel"

    • category (string): "construction"

    • name (string): "Gravel & Crushed Stone Tonnage Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.tons_needed (Gravel Required): Formatted display string (e.g. '8.64 tons')

      • metrics.cubic_yards (Volume (Cubic Yards)): Formatted display string (e.g. '6.17 cu yd')

      • metrics.cubic_feet (Volume (Cubic Feet)): Formatted display string (e.g. '166.7 cu ft')

      • metrics.tandem_loads (Tandem Dump Truck Loads (~14t)): Formatted display string (e.g. '1 truckload')

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

Input Schema

NameRequiredDescriptionDefault
depthNoGravel Depth (in). Compacted layer depth in inches. Default: 4. Min: 1. Max: 24.
widthNoDriveway / Area Width (ft). Width in feet. Default: 10. Min: 1. Max: 100.
lengthNoDriveway / Area Length (ft). Length in feet. Default: 50. Min: 1. Max: 1000.
densityNoAggregate Density (tons/yd³). Crushed limestone ~1.4 tons/yd³. Default: 1.4. Min: 1.1. Max: 1.8.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full load and does it: read-only, idempotent, stateless, no side effects, and out-of-bounds inputs return a diagnostic error status rather than throwing. The only thing not covered is any rate/latency expectation beyond the listed execution_time_ms output field, so it falls just short of a 5.

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?

Heavily sectioned and front-loaded with purpose, which suits an agent reading it programmatically. It loses a point for repetition: floating-point precision is asserted twice (usage and behavior sections), and the RETURNS block is long enough that the metric list could be tighter, but no output schema exists so that detail is largely earned.

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?

No output schema is present, yet the RETURNS section enumerates every field including nested metrics with example formats, and status/error semantics are stated. For a four-parameter, defaults-only, zero-side-effect calculator, nothing an agent needs to call and interpret it is missing.

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 description coverage is already 100% (units, defaults, min/max per parameter), so the baseline would be 3. The description adds real meaning on top by mapping each parameter to its output and stating the formula Tons = Cubic Yards × 1.4, which explains what the density parameter does and how defaults propagate.

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 resource (gravel/crushed stone tonnage) and a specific operation (calculate cubic yards and tons), plus the exact governing formula. Sibling tools are almost all different-domain calculators, so the construction-domain framing is enough to separate it from omni_asphalt_driveway or omni_ac_btu_tonnage without opening a schema.

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?

There is an explicit WHEN TO USE with the exact inputs it consumes, an explicit WHEN NOT TO USE ('qualitative evaluations or unquantified reasoning'), and a DISAMBIGUATION block naming generic dispatchers, batch chaining, and the schema-inspection alternative. The agent is told which sibling to route to for each adjacent need.

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