Skip to main content
Glama

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

Decode a hazmat special provision

hazmat_special_provision
Read-onlyIdempotent

What does a 49 CFR 172.102 special provision code (e.g. 130, A100, IB2, T11) mean? Its full text and what it applies to. 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": {
      "code": "<code>"
    },
    "name": "hazmat_special_provision"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesThe code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered structurally. The description still adds value by stating what comes back — the full regulatory text and what the provision applies to — which no structured field discloses. No auth or rate-limit context, hence not a 5.

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 two sentences are front-loaded and efficient: the question form states purpose, then the return content. The trailing promotional line and UTM-tagged URL ('More APIs from FitzTopPicks') earn no place in a tool definition and dilute an otherwise tight description.

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?

This is a simple single-parameter lookup with no output schema, and the description does explain what the return contains (full text plus applicability). Enough for correct invocation, though it could say more about whether unknown codes error or return empty.

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?

There is a single parameter with 100% schema coverage, so the schema baseline applies. The description does add useful meaning by illustrating the accepted code shapes (numeric like 130, letter-prefixed like A100, and two-letter prefixes like IB2 and T11), which helps avoid malformed input, but it stops short of stating the grammar. A 3 is correct given the schema already documents the parameter.

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 (a 49 CFR 172.102 special provision code) and a concrete operation (decoding it into full text and scope of applicability). The enumerated examples (130, A100, IB2, T11) make the resource unambiguous. It does not explicitly contrast itself with siblings like hazmat_by_un_number or hazmat_search, so it stops short of a 5.

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?

Usage is implied by the opening question: an agent holding a provision code should come here to interpret it. There is no explicit when-not guidance and no named alternative for adjacent lookups (e.g. searching hazmat data by UN number), leaving the routing to inference.

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