Skip to main content
Glama

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

Clearance hole for a bolt

clearance_hole
Read-onlyIdempotent

What size hole lets a bolt pass through (close, normal or loose fit), and its hex head and nut sizes? 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": {
      "thread": "<thread>"
    },
    "name": "clearance_hole"
  }
}

Input Schema

NameRequiredDescriptionDefault
fitNoclose, normal or loose (default: all three).
threadYesThread designation (or just the size: M10, 3/8).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description's added value is modest: it discloses that results include hex head and nut sizes in addition to the hole size, which matters because there is no output schema. It does not mention that omitting 'fit' returns all three fits, or the output unit/system.

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

Conciseness2/5

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

The functional sentence is front-loaded but phrased as a question rather than an instruction, and it is followed by a promotional URL with UTM parameters that consumes roughly half the text and conveys nothing about tool behavior. Trimming the marketing line would make the definition materially tighter.

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 low-complexity two-parameter calculator with no output schema, the description covers the input concept (bolt thread, fit) and, importantly, sketches the return content (hole size, hex head, nut size). Only minor gaps remain, such as stating the default-all-fits behavior and the unit conventions.

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%, so both parameters are already documented, including the 'normal' default for fit and the M10/3/8 thread examples. The description's mention of 'close, normal or loose fit' merely restates the enum. Baseline 3 applies where the schema carries the semantics.

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 concrete outcome — the clearance hole size that lets a bolt pass through, for close/normal/loose fits, plus hex head and nut sizes. That is specific enough to distinguish it from most siblings, though it never mentions the closest relative (drill_bit) or how they differ.

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?

The question framing implies a scenario (you have a bolt thread and need a clearance hole), but there is no explicit when-to-use, no prerequisites, and no routing to alternatives such as drill_bit. The agent is left to infer that this tool is for clearance holes rather than tap/drill sizing.

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