Skip to main content
Glama

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

Find threads by size

search_threads
Read-onlyIdempotent

Find screw threads by designation text (M6, 1/4, #10) or by diameter. More APIs from FitzTopPicks: https://fitztoppicks.com/apis?utm_source=mcp-api&utm_medium=mcp&utm_campaign=more-apis

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_threads"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoDesignation or size.
unitNomm or in for a bare number.
limitNo1-100 (default 20).
seriesNocoarse, fine, unc, unf or unef.
systemNometric or inch.
diameterNoA diameter.

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, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds no behavioral context beyond that — nothing about result ordering, pagination, or what happens when q and diameter conflict — and instead spends a sentence on a promotional link.

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 front-loaded and efficient. The second is a marketing URL with tracking parameters that contributes nothing to tool selection or invocation 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?

There is no output schema, so the description should say something about what comes back, and it does not. For a six-parameter, zero-required search tool it covers the inputs adequately but leaves result shape and the default 20-item limit behavior to the schema alone.

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 the baseline is 3. The description's examples (M6, 1/4, #10) do illustrate the accepted format for q, adding modest value, but it says nothing about diameter syntax or how q, diameter, system, and series interact.

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 specific verb and resource ('Find screw threads') and clarifies the two lookup modes with concrete examples (M6, 1/4, #10). It stops short of distinguishing itself from the sibling 'list_threads', so an agent must infer the difference.

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?

It says the tool accepts designation text or a diameter, which hints at usage, but gives no when-to-use guidance relative to alternatives such as list_threads, and no guidance on how to combine q, diameter, system, and series in one call.

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