Skip to main content
Glama

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

Actual size of nominal lumber

lumber_actual_size
Read-onlyIdempotent

What are the real dimensions of a 2x4 (or 1x6, 4x4, 5/4x6...)? Actual dry or green size of softwood or hardwood lumber, and board feet when a length is given. More APIs from FitzTopPicks: https://fitztoppicks.com/apis?utm_source=mcp-api&utm_medium=mcp&utm_campaign=more-apis

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": {
      "nominal": "<nominal>"
    },
    "name": "lumber_actual_size"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNosoftwood (default) or hardwood.
lengthNoLength in feet (instead of 2x4x8).
nominalYesThe nominal size.
conditionNodry (default) or green (softwood).

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?

The annotations already declare this a read-only, idempotent, closed-world, non-destructive lookup, so the safety profile is fully covered. The description adds that output varies by condition (dry vs. green) and species class (softwood vs. hardwood) and that board feet are returned only when a length is present — genuinely useful behavioral context. It says nothing about output units or formatting, and closes with a promotional link that adds no operational value.

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 opening question is well front-loaded and immediately signals the tool's job, and the second sentence efficiently packs species, condition, and board-feet behavior. The trailing "More APIs from FitzTopPicks" promo sentence is pure noise for an agent and dilutes an otherwise tight definition.

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?

For a simple lookup with full schema coverage and rich annotations, the description covers what the tool returns conceptually (actual dry/green dimensions, optional board feet). With no output schema, however, it omits the one thing an agent most needs to interpret the result: units and precision of the returned dimensions (inches vs. fractional notation). That gap keeps it at minimum-viable rather than 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 100%, so the baseline is 3; the description earns an increment by showing accepted nominal formats ("2x4", "1x6", "4x4", "5/4x6") and clarifying that length can be supplied separately — "instead of 2x4x8" — which explains the relationship between the nominal string and the length parameter. It still doesn't say what units the returned actual size uses.

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 names a specific resource (nominal lumber dimensions) and frames it as a direct question ("What are the real dimensions of a 2x4..."), with examples like 5/4x6 that make the domain unmistakable. It also discloses a secondary output (board feet when length is given). It does not, however, distinguish itself from the sibling tools lumber_sizes or board_feet, which cover overlapping ground.

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 through the example question and the parenthetical "(or 1x6, 4x4, 5/4x6...)" — an agent can infer this is for converting nominal to actual dimensions. There is no explicit statement of when to use this versus lumber_sizes (listing sizes) or board_feet (volume calculation), even though the tool partially duplicates both.

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