Skip to main content
Glama

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

A drill bit by name

drill_bit
Read-onlyIdempotent

The size of a drill bit by name (#7, F, 7/32, 5.5mm), its nearest bit in the other system and the threads it taps. 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": {
      "name": "<name>"
    },
    "name": "drill_bit"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesDrill name.

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, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds real value by disclosing the return content (size, cross-system equivalent, tapped thread) since no output schema exists, but says nothing about error behavior or what happens with an unrecognized name, and spends its second sentence on an unrelated promotional URL.

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 dense and front-loaded with useful information. The second sentence is pure promotion ('More APIs from FitzTopPicks...') with tracking parameters and does nothing to help an agent select or invoke the tool, so roughly half the description is waste.

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 single-parameter lookup, the definition covers input formats and return content, which is close to adequate with no output schema. It remains incomplete on the two things that matter most for selection: how it differs from nearest_drill_bit and what a failed lookup yields.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% so the baseline is 3, and the description earns an extra point by giving concrete accepted name formats ('#7, F, 7/32, 5.5mm'), which tells the agent that both numbered/letter gauges, fractional inches, and metric sizes are valid inputs — semantics the schema's 'Drill name.' text does not convey.

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 (a drill bit identified by name) and enumerates exactly what comes back: its size, the nearest equivalent in the other measurement system, and the thread it taps. That is concrete and specific, but it never distinguishes this tool from the sibling nearest_drill_bit, which appears to cover the same 'nearest bit' functionality.

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, no statement of when to prefer this over nearest_drill_bit (which overlaps on the 'nearest bit in the other system' output), and no mention of constraints or prerequisites. The agent must infer selection criteria from the description alone.

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