Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_drainage_tile_spacing

Calculates subsurface drainage tile lateral spacing, pipe size, water-table drawdown, and installed cost per acre from soil conductivity, drainage coefficient, and installation depth.

Instructions

Agricultural Subsurface Drainage Tile Spacing & Sizing Calculator. Calculate subsurface corrugated HDPE drainage tile lateral spacing in feet, drainage coefficient, and pipe diameter using Hooghoudt's equation. Discipline: AGRICULTURE. Governing mathematical model / formula: Tile Spacing S² = (8 · K · d · h + 4 · K · h²) / Drainage Coefficient (q in/day).

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of recommended_tile_spacing_ft (Optimal Lateral Tile Spacing), linear_feet_tile_per_acre (Required Tile Pipe Per Acre), water_table_drawdown_time (Water Table Drawdown Speed), turnkey_drainage_cost_acre (Est. Installed Cost (@ $1.25/ft)) using soil_hydraulic_cond_in_hr (Soil Hydraulic Conductivity (Inches/Hour) in in/hr), drainage_coefficient_in_day (Drainage Coefficient (Inches/Day) in in/day), tile_installation_depth_ft (Tile Installation Depth (Feet) in 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.

  • SIBLING ROUTING: Use this dedicated specialist tool for 'Agricultural Subsurface Drainage Tile Spacing & Sizing 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): "drainage-tile-spacing"

    • category (string): "agriculture"

    • name (string): "Agricultural Subsurface Drainage Tile Spacing & Sizing Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.recommended_tile_spacing_ft (Optimal Lateral Tile Spacing): Formatted display string (e.g. '45.0 Feet Apart')

      • metrics.linear_feet_tile_per_acre (Required Tile Pipe Per Acre): Formatted display string (e.g. '968 Linear Feet / Acre')

      • metrics.water_table_drawdown_time (Water Table Drawdown Speed): Formatted display string (e.g. '24 Hours (Prevents Root Drowning)')

      • metrics.turnkey_drainage_cost_acre (Est. Installed Cost (@ $1.25/ft)): Formatted display string (e.g. '$1,210.00 / Acre')

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

Input Schema

NameRequiredDescriptionDefault
soil_hydraulic_cond_in_hrNoSoil Hydraulic Conductivity (Inches/Hour) (in/hr). Silty clay ~0.2, silt loam ~0.8, sandy loam ~2.0. Default: 0.8. Min: 0.05. Max: 5.
tile_installation_depth_ftNoTile Installation Depth (Feet) (ft). Average depth from ground surface to tile invert. Default: 3.5. Min: 2.5. Max: 6.
drainage_coefficient_in_dayNoDrainage Coefficient (Inches/Day) (in/day). Standard field crops = 0.38 - 0.50 in/24hr; specialty crops = 0.75 - 1.0 in/24hr. Default: 0.5. Min: 0.25. Max: 1.5.

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 zero annotations, the description carries the full burden and meets it: it declares read-only, idempotent, stateless behavior with no side effects, describes bound-validated inputs returning a diagnostic error status rather than throwing, and reports execution_time_ms. This is the safety and failure-mode profile an agent needs before calling a calculator.

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?

Clearly sectioned and front-loaded with purpose before usage, safety, and returns. A few lines are promotional rather than informational (e.g. 'eliminating LLM arithmetic mistakes and formula hallucinations'), and the formula is stated twice, but the bulk of the text earns its place.

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 exists, so the RETURNS section is necessary and fully enumerates status, calculator metadata, echoed inputs, all four formatted metrics, and timing. Combined with complete parameter coverage and error behavior, an agent has everything required to call and interpret this tool.

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%, with defaults, min/max, and typical soil values already documented in the schema. The description restates the parameter names and units but adds no semantics beyond the schema, so the baseline 3 applies.

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?

Names a specific resource and computation (subsurface drainage tile lateral spacing, drainage coefficient, pipe diameter) and states the governing equation. It also distinguishes itself from the generic dispatcher by name, so an agent can tell it apart from omni_universal_query without opening the 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?

Explicit WHEN TO USE with the three input parameters and the four computed outputs named, an explicit WHEN NOT TO USE (qualitative or non-numeric queries), and explicit sibling routing away from omni_universal_query. Nothing about selection is left to inference.

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