Skip to main content
Glama

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

Common lumber sizes

lumber_sizes
Read-onlyIdempotent

A chart of common nominal lumber sizes with their actual dimensions (softwood or hardwood, dry or green). 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": "lumber_sizes"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNosoftwood (default) or hardwood.
conditionNodry (default) or green.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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. The description adds that results are a lookup chart whose values shift with species and moisture condition, which is genuine context beyond the annotations. It says nothing about how many rows come back or whether the full table is always returned.

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 first sentence is tight and front-loaded, earning its place. The second sentence is a promotional URL with UTM tracking that carries no tool-selection value and dilutes the definition.

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 two-optional-parameter read-only lookup, the description conveys the subject matter and the dimensions that vary the answer. With no output schema present, it also implies the return is a nominal-to-actual mapping table, which is enough for an agent to call it. Only the row count or filtering behavior remains unstated.

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% and both parameters are enums with their own descriptions and stated defaults ('softwood (default)', 'dry (default)'). The description's parenthetical merely restates the two axes without adding format, interaction, or default behavior beyond the schema. Baseline 3 applies.

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?

States a concrete resource and payload: a chart of nominal lumber sizes paired with their actual dimensions. The parenthetical narrows the scope to softwood/hardwood and dry/green variants. It does not distinguish itself from the sibling 'lumber_actual_size', which sounds like it covers adjacent territory.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all — no conditions, prerequisites, or routing to alternatives such as 'lumber_actual_size' or 'board_feet'. The agent must infer the use case purely from the noun phrase.

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