Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_timber_volume_doyle_scribner

Calculates board-foot volume for logs and standing trees using Doyle, Scribner, and International 1/4-inch rules; estimates gross log value from diameter, length, and stumpage price.

Instructions

Timber Board Foot Volume Estimator (Doyle, Scribner & International 1/4). Calculate sawtimber board foot volume (BF) in standing trees and harvested logs using the Doyle, Scribner Decimal C, and International 1/4-Inch log rules. Discipline: AGRICULTURE. Governing mathematical model / formula: Doyle Log Scale = (Diameter at Small End - 4)² × (Length in Feet / 16).

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of doyle_board_feet (Doyle Log Rule Volume), international_board_feet (International 1/4" Rule Volume), scribner_board_feet (Scribner Rule Volume), log_economic_value (Gross Commercial Log Value) using log_small_diameter_in (Log Diameter Inside Bark at Small End (Inches) in in), log_length_feet (Log Length (Feet) in ft), timber_stumpage_price_mbf (Stumpage Price Per 1,000 Board Feet ($/MBF)). 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 'Timber Board Foot Volume Estimator (Doyle, Scribner & International 1/4)' 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): "timber-volume-doyle-scribner"

    • category (string): "agriculture"

    • name (string): "Timber Board Foot Volume Estimator (Doyle, Scribner & International 1/4)"

    • formula (string): Governing mathematical formula string

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

    • metrics (object): Dictionary of computed outputs:

      • metrics.doyle_board_feet (Doyle Log Rule Volume): Formatted display string (e.g. '196 Board Feet (BF)')

      • metrics.international_board_feet (International 1/4" Rule Volume): Formatted display string (e.g. '215 Board Feet (BF)')

      • metrics.scribner_board_feet (Scribner Rule Volume): Formatted display string (e.g. '210 Board Feet (BF)')

      • metrics.log_economic_value (Gross Commercial Log Value): Formatted display string (e.g. '$88.20 / log')

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

Input Schema

NameRequiredDescriptionDefault
log_length_feetNoLog Length (Feet) (ft). Standard commercial log length (typically 12, 14, 16 ft). Default: 16. Min: 8. Max: 24.
log_small_diameter_inNoLog Diameter Inside Bark at Small End (Inches) (in). Scaling diameter measured inside bark. Default: 18. Min: 8. Max: 48.
timber_stumpage_price_mbfNoStumpage Price Per 1,000 Board Feet ($/MBF). Local timber mill price per MBF (e.g. Red Oak / Hard Maple). Default: 450. Min: 100. Max: 2500.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.1/5.0
Behavior4/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 free of side effects, and it explains that out-of-bounds inputs return a safe diagnostic error rather than throwing. It also documents the full return shape (status, calculator, formula, inputs, metrics, execution_time_ms), which is necessary since no output schema exists. Minor gap: no statement about how the three log rules relate to each other or which one is authoritative for a given species/region.

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 well front-loaded — title, formula, and discipline appear before the routing and returns sections — and each block is scannable. There is some duplication: 'machine floating-point precision' is asserted twice, and the parameter names/units are repeated verbatim from the schema, which adds length without new information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given three optional parameters with full schema coverage, no annotations, and no output schema, the description covers everything needed to call the tool correctly: inputs, bounds behavior, determinism, and the exact metrics returned. The one thing left implicit is that all three board-foot rules are computed in a single call and that results are display-formatted strings rather than raw numbers.

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 parameter already carries units, defaults, and min/max bounds in the schema. The description restates the same parameter names and units in the WHEN TO USE block without adding new semantics such as scaling-diameter measurement conventions or how stumpage price interacts with the volume rules. Baseline 3 is appropriate when the schema does the heavy lifting.

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 — calculating sawtimber board foot volume using Doyle, Scribner Decimal C, and International 1/4-Inch rules — and even supplies the governing formula (D - 4)² × L/16. It explicitly distinguishes itself from the generic dispatcher omni_universal_query, so an agent can route to it 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The WHEN TO USE block enumerates the exact computed outputs (doyle_board_feet, scribner_board_feet, international_board_feet, log_economic_value) and the driving inputs, and SIBLING ROUTING names omni_universal_query as the alternative. The WHEN NOT TO USE clause is generic boilerplate ('not for qualitative evaluations') rather than a discriminating exclusion, so it stops just short of a 5.

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