Skip to main content
Glama

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

Tap drill for a thread

tap_drill
Read-onlyIdempotent

Which drill bit do I use to tap this thread (e.g. M8x1.25, 1/4-20) at a given percent of thread? 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": "tap_drill"
  }
}

Input Schema

NameRequiredDescriptionDefault
threadYesThread designation.
percentNoPercent of thread (50-90, default 75).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds nothing beyond the annotations: it does not say what is returned (a drill size? a range?), what units, or how the percent-of-thread value affects the recommendation.

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 functional sentence is front-loaded and short, which is good. The second sentence is an unrelated promotional URL with tracking parameters that adds no decision-relevant information and dilutes the 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 two-parameter read-only calculator with no output schema, the definition is minimally sufficient: the question implies the answer is a drill bit size. It still leaves the return shape and the meaning of the percent default (75) unstated, which matters for an agent reporting results back to a user.

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 both parameters are documented, and the description's examples ('M8x1.25, 1/4-20') usefully show that both metric and imperial thread designations are accepted. It says nothing extra about how 'percent' trades off thread engagement versus drill size, leaving that to the schema.

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 question form 'Which drill bit do I use to tap this thread' states the conversion being performed (thread designation -> tap drill bit) with concrete example inputs. It does not distinguish itself from nearby siblings such as drill_bit, nearest_drill_bit, or clearance_hole, so an agent cannot rule those out from the description alone.

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 explicit when-to-use guidance, no prerequisites, and no named alternative for the related drilling/thread operations that appear in the sibling list. The only implied usage cue is the 'given percent of thread' phrasing, which the schema already exposes.

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