NestingCalc Calculators

hoppus_volume

Hoppus (quarter-girth) volume of round logs from mid-length circumference and length: (C/4)^2 x L. Returns Hoppus volume, true volume (x 4/pi), Hoppus tons (50 h ft3) and a board-feet approximation, with optional quantity and value per Hoppus unit.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "circumference": "<circumference>",
      "length": "<length>"
    },
    "name": "hoppus_volume"
  }
}

Input Schema

Name	Required	Description	Default
`qty`	No
`unit`	No	imperial: circumference in inches, length in feet; metric: cm and m	imperial
`length`	Yes	Log length (ft or m)
`circumference`	Yes	Circumference at mid-length (in or cm)
`price_per_hoppus_unit`	No	Optional value per Hoppus ft3/m3

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 24, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It mentions optional quantity and value calculations, but does not disclose unit handling defaults beyond the schema's 'unit' parameter, nor any limitations (e.g., assumes circular cross-section, no bark deduction). The description adds some value but is not thorough for a calculation tool with no annotations.

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 description is a single sentence that is informative and front-loaded with the calculation method. It covers multiple outputs and options efficiently, though it could be slightly more structured with a list of outputs for readability.

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

Completeness3/5

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

With no output schema, the description must explain return values, which it does (lists Hoppus volume, true volume, tons, board-feet approximation). However, it does not mention what 'true volume' means or how the board-feet approximation is derived, and it omits details about unit conversion defaults. For a domain-specific tool, this is adequate but not fully complete.

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 80%, and the description adds meaning by explaining that 'circumference' is at mid-length and that volume is computed via (C/4)^2 x L. It also clarifies the output units (Hoppus ft3/m3) and optional quantity/value, which helps the agent understand parameter relationships beyond the schema.

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 states a specific verb ('Returns') and resource ('Hoppus volume of round logs') and includes the formula, distinguishing it from siblings like 'log_volume' and 'jas_log_scale' by naming the exact method. It clearly identifies the tool's unique calculation approach.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description implies when to use this tool (for Hoppus/quarter-girth calculations) but does not explicitly state when not to use it or mention alternatives. Given the sibling list includes other log volume calculators, explicit routing would be beneficial.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All NestingCalc Calculators tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?