Fromerica U.S. Trade Data

Find a U.S. Schedule B export code

find_schedule_b

Read-only

Search the official U.S. Census Bureau Schedule B (10-digit export classification used to file Electronic Export Information) by product words or by code prefix. Returns up to 50 codes with their official description and a link to each code's page (unit of quantity, when EEI is required, HS code used abroad, top U.S. export markets).

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": {
      "query": "<query>"
    },
    "name": "find_schedule_b"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Product words (e.g. "frozen shrimp") or a Schedule B code prefix (e.g. "8703.23").

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 27, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already establish a safe read-only, closed-world lookup, so the description's job is to add context — and it does: a hard cap of 50 results, the presence of official descriptions, and per-code links whose pages expose unit of quantity, EEI requirement, HS code, and top markets. It does not say what happens on zero matches or whether the 50-result cap implies truncation the caller must narrow.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, both earning their place: the first establishes identity and input modes, the second establishes output shape and result limit. Front-loaded with the authoritative source and code format.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 must explain returns, and it does — count cap, description field, and link payload. For a single-parameter read-only lookup, an agent has everything needed to invoke it and interpret the response.

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 single 'query' parameter already documents both modes with concrete examples ('frozen shrimp', '8703.23'). The description restates that duality without adding matching behavior details such as prefix depth rules or word-tokenization, so it sits at the baseline.

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 verb ('Search') and a precisely scoped resource ('official U.S. Census Bureau Schedule B ... 10-digit export classification used to file Electronic Export Information'), plus the two supported lookup modes. That scope clearly separates it from the sibling tariff, exporter, and restricted-party tools without needing to name them.

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 tells the agent the two valid query modes (product words or code prefix) and implicitly when the tool applies: classifying a good for export/EEI filing. It stops short of stating exclusions, e.g. that duty rates belong to get_us_tariff/search_us_tariffs rather than here.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Fromerica U.S. Trade Data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?