Skip to main content
Glama

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

Hazmat table rows of a hazard class

hazmat_class_rows
Read-onlyIdempotent

Every 49 CFR 172.101 entry of a hazard class or division (e.g. 3, 2.1, 1.4S, "forbidden"), paged. 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": {
      "class": "<class>"
    },
    "name": "hazmat_class_rows"
  }
}

Input Schema

NameRequiredDescriptionDefault
pgNoOnly packing group I, II, III or none.
classYesClass or division.
limitNo1-500 (default 100).
offsetNoRows to skip.
provisionsNo"full" (each special provision, symbol and vessel code decoded with its text and CFR paragraph) or "codes" (just the codes). Default codes.

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 readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that results are paged, which is useful, but it does not describe ordering, total counts, rate limits, authentication needs, or what fields each row contains.

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 tightly scoped and front-loaded, but the trailing "More APIs from FitzTopPicks" marketing sentence does not help an agent select or invoke the tool and dilutes an otherwise concise definition.

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?

The description covers the dataset, class filter and paging, and the schema fully documents all five parameters. However, with no output schema, it does not explain the shape of returned rows or what an "entry" includes, leaving a meaningful gap for a data-retrieval tool.

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 description coverage is 100%, so the schema already documents pg, limit, offset and provisions. The description still adds meaningful examples for the required class parameter, including "forbidden," which clarifies valid input beyond the schema's brief "Class or division" description.

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 identifies the exact dataset and filter: every 49 CFR 172.101 entry for a hazard class or division, with concrete examples such as 3, 2.1, 1.4S and "forbidden". It is clear what the tool returns, but it does not explicitly distinguish itself from siblings like hazmat_by_un_number or hazmat_search.

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 phrase "Every 49 CFR 172.101 entry of a hazard class or division" and by the examples, so an agent can infer this is the listing-by-class tool. However, there is no explicit when-to-use guidance, no when-not-to-use guidance, and no named alternative for related hazmat lookups.

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