Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_combine_harvester_grain_loss

Calculate combine harvester field grain loss in bushels per acre and lost dollar revenue from kernel counts, crop type, harvested acres, and grain price.

Instructions

Combine Harvester Field Grain Loss & Bushel Dockage Rate Calculator. Calculate field harvesting grain loss in bushels per acre and lost dollar revenue from kernel counts behind combine header and rotor/shoe separator. Discipline: AGRICULTURE. Governing mathematical model / formula: Loss (Bu/Acre) = Counted Kernels Per Square Foot / Kernels per Square Foot per Bushel (Corn = 2, Soybeans = 4, Wheat = 20).

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of bushels_lost_per_acre (Harvest Loss Rate), total_dollar_harvest_loss (Total Dollar Revenue Left in Field), acceptable_loss_status (Combustion Loss Performance), dollar_loss_per_acre (Loss Per Harvested Acre) using kernels_counted_per_sqft (Kernels Counted in 1 Sq Ft Behind Combine in kernels/sq ft), crop_type (Crop Type (1 = Corn, 2 = Soybeans, 3 = Wheat)), harvest_acres_total (Total Harvest Field Acres in acres), commodity_market_price (Grain Cash Price ($/Bushel)). 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 'Combine Harvester Field Grain Loss & Bushel Dockage Rate 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): "combine-harvester-grain-loss"

    • category (string): "agriculture"

    • name (string): "Combine Harvester Field Grain Loss & Bushel Dockage Rate Calculator"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.bushels_lost_per_acre (Harvest Loss Rate): Formatted display string (e.g. '3.0 Bu / Acre')

      • metrics.total_dollar_harvest_loss (Total Dollar Revenue Left in Field): Formatted display string (e.g. '$7,125.00 Lost')

      • metrics.acceptable_loss_status (Combustion Loss Performance): Formatted display string (e.g. 'Unacceptable Loss (> 1.5 Bu/ac)')

      • metrics.dollar_loss_per_acre (Loss Per Harvested Acre): Formatted display string (e.g. '$14.25 / 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_combine_harvester_grain_loss"
  }
}

Input Schema

NameRequiredDescriptionDefault
crop_typeNoCrop Type (1 = Corn, 2 = Soybeans, 3 = Wheat). 1: Corn (2 kernels/sq ft = 1 bu/ac), 2: Soybeans (4 kernels), 3: Wheat (20 kernels). Default: 1. Min: 1. Max: 3.
harvest_acres_totalNoTotal Harvest Field Acres (acres). Total acres harvested. Default: 500. Min: 10. Max: 10000.
commodity_market_priceNoGrain Cash Price ($/Bushel). Local elevator cash grain price. Default: 4.75. Min: 2. Max: 20.
kernels_counted_per_sqftNoKernels Counted in 1 Sq Ft Behind Combine (kernels/sq ft). Count grains on ground inside a 12x12 inch square frame. Default: 6. Min: 0.5. Max: 50.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does so well: it declares the tool read-only, idempotent, stateless with zero side effects, deterministic, and states that out-of-bounds inputs return a diagnostic error instead of throwing. It stops short of documenting cost, rate limits, or whether defaults are applied silently (implied by 'applied defaults' in the returns block).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Section headers make it easy to scan and the core purpose is front-loaded, but there is visible duplication: the floating-point precision guarantee appears both in the usage block and again under BEHAVIOR & SAFETY, and the returns block is long. The odd label 'Combustion Loss Performance' for acceptable_loss_status is also confusing terminology.

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?

For a four-parameter, zero-annotation calculator with no output schema, the definition covers everything an agent needs: inputs and their domains, the formula, error behavior, and a full field-by-field description of the returned JSON metrics and display formats.

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 coverage is 100%, so the four parameters already carry types, bounds, defaults, and descriptions. The definition restates the parameter list and the crop_type kernel-per-bushel mapping, which is useful reinforcement but adds little beyond what the schema already says.

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 first two sentences state a specific verb and resource: compute field grain loss in bushels per acre and lost dollar revenue from kernel counts behind the header and rotor. The governing formula is given explicitly, and the tool is clearly differentiated from generic siblings like omni_universal_query.

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?

There are explicit WHEN TO USE and WHEN NOT TO USE blocks plus a disambiguation section that routes multi-step jobs to omni_batch_calculate and schema inspection to omni_describe_solver. The only weakness is that the exclusion ('qualitative evaluations') is generic rather than agriculture-specific.

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