Skip to main content
Glama

Lumber board footage

bpj_material_lumber_board_feet
Read-onlyIdempotent

Calculate board feet from actual inch thickness and width, linear feet, and piece count.

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": {
      "thickness": "<thickness>",
      "width": "<width>",
      "length": "<length>",
      "quantity": "<quantity>"
    },
    "name": "bpj_material_lumber_board_feet"
  }
}

Input Schema

NameRequiredDescriptionDefault
widthYes
lengthYes
quantityYes
thicknessYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so safety is covered. The description adds a genuinely useful domain nuance by specifying "actual inch" thickness and width rather than nominal dimensions, but it omits the formula and the return unit/precision, leaving some behavioral detail unstated.

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

Conciseness5/5

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

One sentence, front-loaded with the verb and output measure, with zero filler. Every clause contributes either the computed quantity or a required input.

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?

For a pure four-input arithmetic calculator with full annotation coverage and no output schema, the description gives enough to call it correctly. The only shortfall is not stating the expected return unit or rounding, which matters mildly when board footage is fractional.

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 description coverage is 0%, so the description carries the burden and does map all four parameters with units: thickness and width in actual inches, length in linear feet, quantity in pieces. It does not restate ranges or clarify that quantity must be a whole count, but the semantic mapping is otherwise complete.

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?

States a specific verb and resource ("Calculate board feet") plus the exact inputs used (thickness, width, linear feet, piece count), which cleanly separates it from the other material calculators in the sibling list. An agent can identify the operation 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 Guidelines3/5

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

The input listing implicitly tells the agent when the tool applies (you have dimensions in inches, length in feet, and a piece count), but there is no explicit when-to-use or when-not-to-use statement and no named alternative such as a nominal-vs-actual sizing helper. Adequate but inferential.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.