Skip to main content
Glama

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

Hazmat table rows for a UN number

hazmat_by_un_number
Read-onlyIdempotent

What does the US hazardous materials table (49 CFR 172.101) say for a UN/NA number (e.g. UN1993)? Proper shipping name, hazard class, packing group, labels, special provisions decoded, packaging sections and quantity limits. 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": {
      "id": "<id>"
    },
    "name": "hazmat_by_un_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesUN1993, NA1993, ID8000 or 1993.
provisionsNo"full" (each special provision, symbol and vessel code decoded with its text and CFR paragraph) or "codes" (just the codes). Default full.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful content context (decoded special provisions with text and CFR paragraph, packaging sections, quantity limits) but says nothing about behavior on an invalid/unknown UN number or how rows are ordered. A modest add over the annotations.

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 well front-loaded and the enumerated payload list is efficient. The trailing 'More APIs from FitzTopPicks' line with UTM parameters is promotional noise that 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?

For a two-parameter lookup with no output schema, the description conveys enough about the returned fields that an agent knows what to expect, and the schema covers parameter formats. Only the omission of failure/empty-result behavior keeps it from being fully complete.

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 the schema already explains the id formats (UN1993/NA1993/ID8000/1993) and the full-vs-codes enum. The description reinforces the decoded-provisions behavior with 'special provisions decoded', matching the default 'full', but adds no syntax or format detail beyond the schema. Baseline 3 applies.

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?

Names a specific resource (the 49 CFR 172.101 hazardous materials table) and the lookup key (UN/NA number), and enumerates what comes back: proper shipping name, hazard class, packing group, labels, special provisions, packaging sections and quantity limits. That is far more specific than a restated title. It does not explicitly distinguish itself from siblings like hazmat_class_rows or hazmat_search, which keeps it off 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?

The example 'UN1993' and the framing 'for a UN/NA number' imply the lookup use case, but there is no statement of when to choose this over hazmat_search or hazmat_class_rows, and no prerequisites or edge-case guidance (e.g. unknown numbers). Usage is inferable but not stated.

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