Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_pavers

Calculates paver counts, bedding sand, crushed base gravel, and polymeric joint sand for patios and walkways from area dimensions and paver size.

Instructions

Patio Paver & Polymeric Sand Calculator. Calculate stone pavers, bedding sand, crushed stone base, and joint sand requirements for patios and walkways. Discipline: CONSTRUCTION. Governing mathematical model / formula: Paver Units = Area (sq ft) / Paver Area (sq ft) × 1.10.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of pavers_count (Pavers to Order (10% Waste)), bedding_sand (1" Bedding Sand (cu yd)), base_gravel (4" Crushed Base Gravel (tons)), polymeric_sand (Polymeric Sand (50 lb Bags)) using length (Patio Length in ft), width (Patio Width in ft), paver_length (Paver Unit Length in in), paver_width (Paver Unit Width in in). 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 'Patio Paver & Polymeric Sand 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): "pavers"

    • category (string): "construction"

    • name (string): "Patio Paver & Polymeric Sand Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.pavers_count (Pavers to Order (10% Waste)): Formatted display string (e.g. '1,485 pavers')

      • metrics.bedding_sand (1" Bedding Sand (cu yd)): Formatted display string (e.g. '0.93 cu yd')

      • metrics.base_gravel (4" Crushed Base Gravel (tons)): Formatted display string (e.g. '5.19 tons')

      • metrics.polymeric_sand (Polymeric Sand (50 lb Bags)): Formatted display string (e.g. '3 bags')

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

Input Schema

NameRequiredDescriptionDefault
widthNoPatio Width (ft). Width of paver patio in feet. Default: 15. Min: 2. Max: 100.
lengthNoPatio Length (ft). Length of paver patio in feet. Default: 20. Min: 2. Max: 100.
paver_widthNoPaver Unit Width (in). Paver width in inches. Default: 4. Min: 4. Max: 24.
paver_lengthNoPaver Unit Length (in). Paver length in inches. Default: 8. Min: 4. Max: 24.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

Score is being calculated.

Deploy Server

Other Tools