Skip to main content
Glama

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

Search the hazmat table by name

hazmat_search
Read-onlyIdempotent

Find hazardous materials by proper shipping name (fuzzy, e.g. "acetone", "lithium batteries") in the 49 CFR 172.101 table, with their UN numbers and classes. 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": {
      "name": "<name>"
    },
    "name": "hazmat_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesShipping name or part of one (up to 120 characters). "q" works too.
classNoOnly this hazard class or division (3, 2.1, 1.4S, forbidden...).
limitNoResults (1-50, default 10).

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 readOnly, idempotent, non-destructive and closed-world, so the description needn't repeat the safety profile. It adds genuinely new context: the results are fuzzy matches, the backing data set is 49 CFR 172.101, and records carry UN numbers and hazard classes.

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 information-dense. The second sentence is a marketing link with UTM tracking parameters that adds no value for tool selection and dilutes the definition.

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?

With no output schema, the description carries the burden of describing returns, and it does specify UN numbers and hazard classes. Result ordering and truncation behavior are not covered, but the essentials for calling the tool correctly are present.

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 description coverage is 100%, so the schema already documents name, class and limit, including bounds and defaults. The description contributes only illustrative query examples ('acetone', 'lithium batteries'), which help but do not add syntax or semantics beyond the schema.

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?

States a specific verb and resource: find hazardous materials by proper shipping name in the 49 CFR 172.101 table, returning UN numbers and classes. That scope distinguishes it in practice from a UN-number lookup, though no sibling is named, so the differentiation is implied rather than explicit.

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?

Vocabulary ('proper shipping name', fuzzy matching examples) implies when to reach for this tool, but there is no explicit statement of when to prefer it over a UN-number or class-based lookup, nor any exclusion conditions.

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