Skip to main content
Glama

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

Nearest standard drill bit

nearest_drill_bit
Read-onlyIdempotent

Which standard drill bit (fractional, number, letter or metric) is closest to a size like 5.1 mm or 0.201 in? 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": {
      "size": "<size>"
    },
    "name": "nearest_drill_bit"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeYesA length.
unitNomm or in, for a bare number.
systemNoWhich bits.

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 readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds that matching spans multiple standards (fractional/number/letter/metric), but says nothing about what happens on an ambiguous or out-of-range size, nor about the response shape.

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 a well-formed, front-loaded purpose statement with concrete examples. The second sentence is a promotional URL unrelated to invoking the tool, which 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 read-only calculator this covers the input domain adequately, but with no output schema the description should say what comes back (bit designation, size, match tolerance). That omission matters because the whole value of the tool is the returned match.

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 the schema already documents all three parameters, making 3 the baseline. The examples '5.1 mm' and '0.201 in' give useful format hints and imply unit can be embedded in the size string, but nothing is said about what 'system' accepts beyond 'Which bits'.

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 states a specific question the tool answers — the closest standard drill bit for a given size — and enumerates the four bit systems (fractional, number, letter, metric). It does not distinguish itself from the sibling 'drill_bit' or 'tap_drill', so an agent cannot be fully certain which bit-lookup tool to pick.

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 implied by the phrasing 'closest to a size like 5.1 mm or 0.201 in', which signals a size-to-bit conversion task. There is no when-not guidance and no mention of when to prefer 'drill_bit' or 'tap_drill' instead, leaving the sibling disambiguation to inference.

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