Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_grain_bin_bushel_capacity

Calculate struck and peaked bushel capacity for round grain bins from diameter, eave height, cone setting, and pack factor; also returns corn storage weight in metric tons.

Instructions

Grain Silo & Cylindrical Grain Bin Bushel Capacity Calculator. Calculate struck and peaked grain volume in bushels for round corrugated steel grain bins, accounting for grain compaction and test weight pack factors. Discipline: AGRICULTURE. Governing mathematical model / formula: Cylinder Bushels = 0.6284 × Diameter² × Eave Height | Peak Cone Bushels = 0.2094 × Diameter² × Peak Cone Height.

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of total_bushels_stored (Total Grain Capacity (Peaked)), struck_level_bushels (Level Struck Bushels (Eave Height)), peaked_cone_bushels (Roof Peak Cone Volume), total_grain_metric_tons (Corn Storage Weight (@ 56 lb/Bu)) using bin_diameter_ft (Bin Diameter (Feet) in ft), bin_eave_height_ft (Eave Wall Height (Feet) in ft), peaked_grain_cone (Grain Peaked to Roof Peak (1 = Peaked, 0 = Struck Level)), grain_pack_factor_pct (Grain Compaction Pack Factor (%) 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 'Grain Silo & Cylindrical Grain Bin Bushel Capacity 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): "grain-bin-bushel-capacity"

    • category (string): "agriculture"

    • name (string): "Grain Silo & Cylindrical Grain Bin Bushel Capacity Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.total_bushels_stored (Total Grain Capacity (Peaked)): Formatted display string (e.g. '22,460 Bushels')

      • metrics.struck_level_bushels (Level Struck Bushels (Eave Height)): Formatted display string (e.g. '19,545 Bushels')

      • metrics.peaked_cone_bushels (Roof Peak Cone Volume): Formatted display string (e.g. '2,915 Bushels')

      • metrics.total_grain_metric_tons (Corn Storage Weight (@ 56 lb/Bu)): Formatted display string (e.g. '570.5 Metric 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_grain_bin_bushel_capacity"
  }
}

Input Schema

NameRequiredDescriptionDefault
bin_diameter_ftNoBin Diameter (Feet) (ft). Inside diameter of corrugated steel wall. Default: 36. Min: 12. Max: 105.
peaked_grain_coneNoGrain Peaked to Roof Peak (1 = Peaked, 0 = Struck Level). 1 if grain is mounded into roof peak cone (typically 30° roof pitch). Default: 1. Min: 0. Max: 1.
bin_eave_height_ftNoEave Wall Height (Feet) (ft). Height from concrete foundation to roof ring eave. Default: 24. Min: 10. Max: 80.
grain_pack_factor_pctNoGrain Compaction Pack Factor (%) (%). Compaction increase from depth and test weight (typically 4% - 6%). Default: 5. Min: 0. 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 behavioral burden and does so thoroughly: it states the tool is read-only, idempotent, stateless, and side-effect free. It also explains input-bound validation and that out-of-range arguments return a safe diagnostic error rather than throwing.

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 structured and front-loaded with purpose, formulas, usage, boundaries, and returns. Some material is redundant across the formula line, usage section, and returns section, but the structure makes it easy to scan.

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?

Although there is no output schema, the description fully documents the structured JSON response, including status, echoed inputs, metric names, and execution timing. Combined with formulas, bounds, and error behavior, it gives an agent everything needed to invoke and interpret the tool.

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 would be 3, but the description adds useful meaning by tying parameters to the governing formulas: diameter and eave height drive cylinder bushels, while peaked cone height drives cone bushels. It also maps the binary peaked_grain_cone switch and pack-factor percentage to domain concepts, though it largely repeats schema labels for units and defaults.

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 resource and operation: bushel capacity for round corrugated grain bins, including struck and peaked volume. It also explicitly distinguishes this specialist calculator from generic dispatchers like omni_universal_query and from batch execution via omni_batch_calculate.

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 provides explicit WHEN TO USE and WHEN NOT TO USE sections, naming the exact outputs and inputs involved. Alternatives are also named for generic dispatch and multi-calculation workflows, leaving little ambiguity about tool selection.

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