Skip to main content
Glama

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

Plywood, OSB and drywall sheets

sheet_goods
Read-onlyIdempotent

Real thickness of plywood, OSB or drywall, and how many 4x8 (or other) sheets cover an area with waste. 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": "sheet_goods"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoArea to cover.
sizeNoSheet size in feet.
typeNoplywood, osb or drywall.
wasteNoWaste percent, 0-50 (default 10).
nominalNoThickness as sold, inches.
areaUnitNoft2 (default) or m2.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this a pure, read-only, idempotent, closed-world computation, so the safety bar is low. The description adds the useful hint that thickness is reported as 'real' rather than nominal, but says nothing about how defaults (waste 10%, ft2) are applied or what the returned numbers look like.

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 front-loaded and informative about the two outputs. The second sentence is a promotional link with UTM tracking that provides no value for tool selection or invocation and should not be there.

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 and six parameters, the description should clarify the return shape; it names the two results (thickness and sheet count) but not their form or units. For a simple calculator this is close to adequate, but a sentence on what comes back would close the gap.

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 description coverage is 100% and enums constrain size, type, and areaUnit, so the schema carries parameter meaning. The description's only added semantic is the nominal-versus-real thickness distinction, which hints at why 'nominal' exists but does not explain the conversion.

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 the resource (plywood, OSB, drywall sheets) and the two outputs it produces: real thickness and sheet count for an area including waste. That is a concrete purpose an agent can match to a request, though it never explicitly distinguishes itself from adjacent calculators like board_feet or concrete_calculator.

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 by the subject matter: you call it when you need panel counts or actual thickness. There is no statement of when to prefer it over a sibling estimator, no prerequisites, and no exclusions, so the agent must infer the routing itself.

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