Skip to main content
Glama

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

Every standard thread

list_threads
Read-onlyIdempotent

Every standard metric and inch screw thread (compact), filtered by system or series. 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": "list_threads"
  }
}

Input Schema

NameRequiredDescriptionDefault
seriesNocoarse, fine, unc, unf or unef.
systemNometric or inch.

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, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only that results are standard (non-pipe) threads and 'compact', which is unexplained and does not clarify result volume, pagination, or whether a full unfiltered list is returned.

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 brief, but the trailing promotional line with a UTM-tagged URL consumes roughly half the text and contributes nothing to tool selection. The parenthetical '(compact)' is undefined filler.

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-optional-parameter read-only listing with a fully described schema and complete annotations, most of the calling contract is already covered by structured fields. What remains missing is any sense of result scope (how many threads, whether all are returned) and what 'compact' means.

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 (series, system) have descriptions plus an enum on system, so the schema does the heavy lifting. The description's 'filtered by system or series' merely restates the parameter names without adding allowed values or combination behavior, which is the baseline for full coverage.

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 resource ('every standard metric and inch screw thread') with a stated scope and filter dimension, so an agent knows this is a thread catalog listing rather than a lookup. It does not distinguish itself from the related search_threads, npt_pipe_thread, or thread_info siblings, leaving ambiguity about which thread 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?

'Filtered by system or series' implies how to narrow results but never states when this listing is preferable to search_threads or why NPT/pipe threads are excluded. No exclusions or alternatives are named, so routing must be inferred from sibling names 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