Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_detention_pond_settling_volume

Calculate required stormwater detention basin storage volume, footprint, and peak flow attenuation from post- and pre-development runoff peaks and storm duration.

Instructions

Stormwater Detention Basin Storage Volume & Settling Inflow Calculator. Calculate required active flood retention storage volume (acre-feet and cubic feet) and orifice release diameter for post-development stormwater mitigation. Discipline: ENGINEERING. Governing mathematical model / formula: Storage Volume V_s = (Runoff Volume Post - Runoff Volume Pre) | Inflow Hydrograph Routing.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of required_retention_storage_cuft (Required Active Storage Volume), required_storage_acre_feet (Storage in Acre-Feet), pond_footprint_half_depth (Pond Water Surface Area (@ 4 ft depth)), discharge_reduction_pct (Peak Flow Attenuation) using post_development_peak_cfs (Post-Development Peak Runoff (Q_post in CFS) in CFS), pre_development_target_cfs (Pre-Development Allowable Discharge (Q_pre in CFS) in CFS), storm_duration_hours (Design Storm Duration (Hours) in hours). 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 'Stormwater Detention Basin Storage Volume & Settling Inflow 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): "detention-pond-settling-volume"

    • category (string): "engineering"

    • name (string): "Stormwater Detention Basin Storage Volume & Settling Inflow Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.required_retention_storage_cuft (Required Active Storage Volume): Formatted display string (e.g. '108,000 cu ft')

      • metrics.required_storage_acre_feet (Storage in Acre-Feet): Formatted display string (e.g. '2.48 Acre-Feet')

      • metrics.pond_footprint_half_depth (Pond Water Surface Area (@ 4 ft depth)): Formatted display string (e.g. '27,000 sq ft (0.62 Acres)')

      • metrics.discharge_reduction_pct (Peak Flow Attenuation): Formatted display string (e.g. '57.1% Flow Reduction')

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

Input Schema

NameRequiredDescriptionDefault
storm_duration_hoursNoDesign Storm Duration (Hours) (hours). Critical duration for peak storage requirement. Default: 2.5. Min: 1. Max: 24.
post_development_peak_cfsNoPost-Development Peak Runoff (Q_post in CFS) (CFS). Unmitigated 25-year post-construction peak flow. Default: 42. Min: 5. Max: 500.
pre_development_target_cfsNoPre-Development Allowable Discharge (Q_pre in CFS) (CFS). Pre-existing natural pasture/forest peak discharge limit. Default: 18. Min: 2. Max: 250.

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 supplied, the description carries the full burden and does so: it declares read-only, idempotent, stateless behavior with zero side effects, describes input validation against physical bounds, and specifies that out-of-bounds inputs return a diagnostic error rather than throwing. That is the behavioral profile an agent needs before calling a mutation-adjacent engineering tool.

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?

Section headers (USAGE GUIDELINES, DISAMBIGUATION, BEHAVIOR & SAFETY, RETURNS) front-load the decision-relevant content, which is good structure for a definition this size. It loses a point for redundancy: the machine-precision determinism claim appears twice and the RETURNS section restates the tool name and category already given at the top.

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, so the description must and does document the entire return payload down to individual metric keys, their units, and sample formatted values, plus status and error semantics. For a deterministic three-input calculator this is everything an agent needs to call it and interpret the result.

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%, and each of the three parameters already carries units, defaults, and min/max in the schema; the description mostly restates those names and units. It does add the governing relation V_s = (Post Runoff − Pre Runoff) which hints at how the inputs interact, but no additional parameter-level guidance (e.g. how storm_duration_hours drives the critical duration) beyond what the schema provides.

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 opening line names a specific verb and resource ("Calculate required active flood retention storage volume ... and orifice release diameter") and enumerates the exact outputs (required_retention_storage_cuft, required_storage_acre_feet, pond_footprint_half_depth, discharge_reduction_pct). It also states the governing model, so an agent can tell it apart from neighboring engineering calculators 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?

The description has explicit WHEN TO USE and WHEN NOT TO USE blocks, plus a disambiguation section naming three concrete alternatives (omni_batch_calculate, omni_describe_solver, omni_universal_query) and the conditions that select them. The exclusion ("no qualitative evaluations; all inputs must be numeric") is unambiguous.

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