Skip to main content
Glama

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

Everything about a screw thread

thread_info
Read-onlyIdempotent

Dimensions of a screw thread (M6x1, 1/4-20 UNC, #10-32...): pitch, diameters, tap drill, clearance holes and hex 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": {
      "designation": "<designation>"
    },
    "name": "thread_info"
  }
}

Input Schema

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

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. The description adds the useful fact that the tool computes derived values (tap drill, clearance holes, hex sizes), but says nothing about behavior on an unrecognized or malformed designation or about rounding/standard conventions used.

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 the useful field list. The second sentence is a promotional URL for other APIs with UTM tracking parameters, which earns no place in a tool definition and dilutes the signal.

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?

With no output schema, the description properly compensates by enumerating the returned measurements. For a two-parameter lookup tool this is close to sufficient; the remaining gap is guidance on invalid designations and on which thread standards are supported.

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% and both parameters are documented there, including the 50-90 range and 75 default for percent. The description contributes designation format examples, which help an agent format input correctly, but it never mentions the percent parameter or how thread engagement affects the returned values.

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 (screw thread dimensions) and enumerates the specific outputs: pitch, diameters, tap drill, clearance holes and hex sizes, with concrete designation examples (M6x1, 1/4-20 UNC, #10-32). That is far more specific than the title. It does not, however, distinguish itself from siblings such as npt_pipe_thread or clearance_hole, even though it returns clearance-hole data.

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 at all: no statement that this covers metric/inch machine threads while npt_pipe_thread covers pipe threads, and no note about when to call clearance_hole instead. The designation examples imply usage context but leave the agent to infer the boundaries.

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