Johto Data

Johto Data US Trade Rules Monitor | 美国贸易法规监测

us_trade_rule_monitor

Read-only

Search Federal Register trade and regulatory publication metadata. Dates, agencies and official PDF links. Not legal advice. Costs $0.002 USDC per call via x402. Without payment, the call returns the x402 payment requirements; retry with an X-PAYMENT or PAYMENT-SIGNATURE header, or params._meta["x402/payment"].

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": "us_trade_rule_monitor"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum records / 最大记录数
`query`	Yes	English product/regulatory keyword or HTS code / 英文关键词

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026

TDQS

A3.9/5.0

Behavior5/5

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

Goes well beyond the readOnlyHint annotation by disclosing a metered cost ($0.002 USDC via x402) and the exact failure/retry protocol: an unpaid call returns payment requirements, and the retry must carry X-PAYMENT/PAYMENT-SIGNATURE or params._meta["x402/payment"]. That payment/auth behavior is decisive for an agent and is unavailable anywhere in the structured fields.

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

Conciseness4/5

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

Front-loads what the tool returns before the commercial and payment mechanics, and uses short declarative sentences with no filler. It is terse to the point of being telegraphic, but every clause carries operational information.

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 read-only search with no output schema, the description covers the source, the returned metadata, the disclaimer, and the complete payment flow. Only the absence of result-shape or pagination detail 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%, so both 'query' and 'limit' are already fully documented in the schema. The description adds no extra syntax, keyword, or HTS-code guidance for 'query', so the 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 verb ('Search') and a specific resource ('Federal Register trade and regulatory publication metadata'), and even previews the returned fields (dates, agencies, PDF links). It does not explicitly distinguish itself from related siblings such as us_hts_tariff_lookup or trade_compliance_pack, 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 only implied: an agent can infer this is the tool for regulator-published notices, but there is no explicit when-to-use/when-not statement and no routing to alternatives. The 'Not legal advice' caveat is a scope hint rather than selection guidance.

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

All Johto 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?