Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_gutter_sizing

Calculate rain gutter size, downspout count, design drainage area, and peak stormwater flow from roof dimensions, pitch, and local rainfall intensity.

Instructions

Rain Gutter & Downspout Sizing Calculator. Calculate roof drainage watershed, 5-inch vs 6-inch seamless K-style gutter capacity, and downspout count based on local rainfall intensity. Discipline: CONSTRUCTION. Governing mathematical model / formula: Drainage Area = Roof Area × Pitch Factor × Max Rainfall Rate (in/hr).

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of gutter_profile (Recommended Gutter Size), downspouts_count (Downspouts Required), adjusted_area (Design Watershed Drainage Area), peak_flow_rate (Peak Stormwater Discharge) using roof_length (Eave Gutter Length in ft), roof_width (Roof Width (Ridge to Eave) in ft), rainfall_intensity (10-Year Max Rainfall Rate in in/hr), roof_pitch (Roof Pitch Rise (/12)). 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 'Rain Gutter & Downspout 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): "gutter-sizing"

    • category (string): "construction"

    • name (string): "Rain Gutter & Downspout Sizing Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.gutter_profile (Recommended Gutter Size): Formatted display string (e.g. '6-Inch K-Style')

      • metrics.downspouts_count (Downspouts Required): Formatted display string (e.g. '2 Downspouts (3×4")')

      • metrics.adjusted_area (Design Watershed Drainage Area): Formatted display string (e.g. '1,080 sq ft')

      • metrics.peak_flow_rate (Peak Stormwater Discharge): Formatted display string (e.g. '61.9 GPM')

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

Input Schema

NameRequiredDescriptionDefault
roof_pitchNoRoof Pitch Rise (/12). Pitch multiplier accounts for wind-driven rain velocity. Default: 6. Min: 2. Max: 16.
roof_widthNoRoof Width (Ridge to Eave) (ft). Horizontal span draining into this gutter. Default: 20. Min: 5. Max: 80.
roof_lengthNoEave Gutter Length (ft). Length of fascia board along roof eave. Default: 45. Min: 10. Max: 200.
rainfall_intensityNo10-Year Max Rainfall Rate (in/hr). US average: 4.0 to 6.5 inches/hr peak storm. Default: 5.5. Min: 2. Max: 10.

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?

With no annotations supplied, the description carries the full burden and does so: it declares the tool read-only, idempotent, stateless, and deterministic, and states that out-of-bounds inputs return a diagnostic error status rather than throwing. It also documents the full return envelope, including that metrics are pre-formatted display strings, which prevents downstream parsing mistakes.

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?

The definition is long but well-sectioned and front-loaded: purpose, guidelines, behavior, returns, with no buried critical information. Some lines are boilerplate that would apply to any calculator in the family (the generic WHEN NOT TO USE clause), which is the main thing keeping it from a 5.

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 RETURNS block is essential and is present in detail, listing every top-level field and each computed metric with an example format. Combined with the validation and determinism guarantees, an agent has everything needed to call this correctly and interpret the result.

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 coverage is 100%, so the baseline is 3, but the description adds value by tying each parameter to the metric it drives (e.g. roof_length and roof_width feed adjusted_area, rainfall_intensity feeds peak_flow_rate). It largely mirrors the schema's units and defaults rather than extending them, which keeps it just short of a 5.

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 verb and resource ('Rain Gutter & Downspout Sizing Calculator') and enumerates the exact outputs (gutter profile, downspout count, adjusted drainage area, peak flow). It also explicitly distinguishes itself from generic dispatchers like omni_universal_query, so an agent can separate it from siblings 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?

It gives an explicit WHEN TO USE list mapping each input parameter to its corresponding computed output, a WHEN NOT TO USE exclusion (qualitative or non-numeric reasoning), and explicit sibling routing to omni_universal_query for cross-discipline dispatch. Nothing about invocation conditions 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