Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_sod_turf

Calculate sod pallets, rolls, lawn square footage, and estimated weight from lawn dimensions and pallet size to avoid arithmetic mistakes in turfgrass ordering.

Instructions

Sod & Turf Pallet Calculator. Calculate sod rolls, square feet, pallet counts, and soil prep requirements for instant lawn turfgrass. Discipline: CONSTRUCTION. Governing mathematical model / formula: Pallets Needed = [Lawn Sq Ft × 1.05] / Pallet Sq Ft (Typically 450).

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of pallets_needed (Pallets to Order (5% Waste)), total_sqft (Total Lawn Surface Area), sod_rolls (Individual Rolls (2' × 5')), estimated_weight (Approx. Pallet Weight) using length (Lawn Length in ft), width (Lawn Width in ft), pallet_sqft (Sq Ft per Pallet in sq ft). 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 'Sod & Turf Pallet 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): "sod-turf"

    • category (string): "construction"

    • name (string): "Sod & Turf Pallet Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.pallets_needed (Pallets to Order (5% Waste)): Formatted display string (e.g. '8 pallets')

      • metrics.total_sqft (Total Lawn Surface Area): Formatted display string (e.g. '3,200.0 sq ft')

      • metrics.sod_rolls (Individual Rolls (2' × 5')): Formatted display string (e.g. '336 rolls')

      • metrics.estimated_weight (Approx. Pallet Weight): Formatted display string (e.g. '16,000 lbs (8.0 tons)')

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

Input Schema

NameRequiredDescriptionDefault
widthNoLawn Width (ft). Lawn width in feet. Default: 40. Min: 5. Max: 500.
lengthNoLawn Length (ft). Lawn length in feet. Default: 80. Min: 5. Max: 500.
pallet_sqftNoSq Ft per Pallet (sq ft). Standard pallet: 450-500 sq ft (50 rolls). Default: 450. Min: 400. Max: 500.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.8/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 so: it declares the tool read-only, idempotent, stateless, deterministic floating-point, and specifies that out-of-bounds inputs return a safe diagnostic error rather than throwing. The error/success contract via the status field is also disclosed.

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?

Well front-loaded with a one-line purpose, then formula, then labelled sections for guidelines, boundaries, safety and returns — easy to scan. Minor redundancy in 'Read-only, idempotent, and stateless. Zero side effects or persistent state mutations,' which says the same thing twice, and the RETURNS section is long relative to the three-parameter surface.

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?

There is no output schema, yet the description fully documents the return envelope — status, calculator, category, formula, echoed inputs, and each metrics field with units and example formatting. Combined with the formula and validation behavior, an agent has everything needed to call and interpret this tool correctly.

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 100%, so the baseline is 3; the description adds value by tying each parameter to its role in the formula (length, width, pallet_sqft feeding pallets_needed and total_sqft) and naming the 5% waste factor that explains the 1.05 multiplier. It does not restate the numeric bounds, which the schema already handles.

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 set — calculate sod rolls, square feet, pallet counts and soil prep for turfgrass — and gives the governing formula (Pallets Needed = [Lawn Sq Ft × 1.05] / 450). It is immediately distinguishable from generic siblings like omni_universal_query and from adjacent calculators.

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 has an explicit WHEN TO USE block enumerating the exact outputs and inputs, a WHEN NOT TO USE clause excluding qualitative reasoning and non-numeric inputs, and a disambiguation section routing chained jobs to omni_batch_calculate and schema inspection to omni_describe_solver.

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