Skip to main content
Glama

FitzTopPicks APIs: calendars, recipes, names, places, sizes and more

Board feet and lumber cost

board_feet
Read-onlyIdempotent

How many board feet (and linear feet, volume and cost) are in some boards? From a nominal size or thickness and width, length and quantity, with a price per board foot, linear foot or piece. More APIs from FitzTopPicks: https://fitztoppicks.com/apis?utm_source=mcp-api&utm_medium=mcp&utm_campaign=more-apis

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": "board_feet"
  }
}

Input Schema

NameRequiredDescriptionDefault
qtyNoPieces, 1-100000 (default 1).
typeNosoftwood (default) or hardwood.
basisNonominal (default) or actual.
priceNoA price.
widthNoWidth in inches.
lengthNoLength (feet by default).
nominalNoNominal size, optionally with the length in feet.
conditionNodry or green, for basis=actual.
priceUnitNobf (default), mbf, lf or piece.
thicknessNoThickness in inches.
lengthUnitNoft (default), in or m.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered externally. The description adds that results include multiple derived values (board feet, linear feet, volume, cost), but it says nothing about precision/rounding, unit handling, or what happens when conflicting inputs (nominal vs thickness/width) are supplied.

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?

The computational part is front-loaded and reasonably tight, but the second sentence is promotional boilerplate ('More APIs from FitzTopPicks...') with a tracking URL that does not help an agent invoke the tool. Removing it would make the definition notably cleaner.

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 stateless calculator with strong annotations and a fully described 11-parameter schema, the description is largely complete: it names the inputs and the outputs. The missing piece is guidance on input combinations (nominal shortcut vs explicit thickness/width, and how basis/condition/hardwood interact), but the schema carries most of that burden.

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 schema already documents every parameter including defaults and enums. The description adds only mild context by grouping price per board foot, linear foot, or piece, which hints at priceUnit, and by framing nominal size as an alternative to thickness+width. That is baseline-level value, not compensation-worthy detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific phrasing ('How many board feet ... are in some boards?') and enumerates the outputs (board feet, linear feet, volume, cost) plus the shape of the inputs (nominal size or thickness/width, length, quantity, price unit). This clearly separates it from siblings like lumber_sizes and lumber_actual_size. It stops short of a single crisp verb+resource statement, but an agent can identify the tool's job.

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?

Usage is only implied: the tool is for computing board feet and cost from board dimensions. There is no explicit statement of when to prefer it over lumber_actual_size or lumber_sizes, no note about which input combination is valid (nominal vs thickness+width), and no exclusions.

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.

Resources