Skip to main content
Glama

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

NPT pipe thread

npt_pipe_thread
Read-onlyIdempotent

NPT tapered pipe thread dimensions and tap drill for a pipe size (1/2-14 NPT...), or the list of sizes when none is given. 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": "npt_pipe_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNoNominal pipe size, 1/16 to 2 (optional).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/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 one genuine behavioral fact beyond them: the no-argument call returns a list of sizes rather than an error. It says nothing about output shape or units beyond the example, which is acceptable for a trivial read tool.

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 content is a single front-loaded sentence with zero waste. The second sentence is promotional boilerplate pointing to an unrelated API catalog, which consumes roughly half the text without helping an agent invoke the tool.

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?

For a one-optional-parameter read-only lookup with no output schema, the definition covers both call modes and gives an example input format, so an agent can invoke it correctly. The only shortfall is the absence of any statement about the returned fields or units, which is minor for a deterministic table lookup.

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; the description earns a bump by supplying a concrete value format example ('1/2-14 NPT') that shows how the string should be written, something the schema's 'Nominal pipe size, 1/16 to 2' does not demonstrate. It still does not discuss tolerance in matching or what happens with an unrecognized size.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (NPT tapered pipe thread dimensions and tap drill) and states exactly what is returned in both modes: per-size data when a pipe size is supplied, or the size list when it is not. An agent can tell this apart from generic lookup siblings without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It resolves the main selection ambiguity for a tool with an optional parameter by explicitly stating that omitting the size returns the list of available sizes, which tells the agent how to discover valid inputs. It stops short of naming alternatives such as thread_info or stating when this tool should not be used.

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