TradeStats - customs trade statistics

report_data_issue

Report a figure that looks wrong or a data problem you noticed (at most 10 reports per day per caller). Give the tool and arguments of the call in question and describe the problem in message (up to 2,000 characters). Returns a report id; the text is stored for review by the operator and is never shown to other users. Use it only after checking the figure; not for questions or feature requests. Look at get_catalog or the notes of an answer first: gaps and non-comparable periods are often documented there.

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": {
      "message": "<message>"
    },
    "name": "report_data_issue"
  }
}

Input Schema

Name	Required	Description
`args`	No	The arguments of that call (at most 4 KB as JSON).
`tool`	No	Name of the tool whose answer looked wrong, e.g. "get_series".
`message`	Yes	What looks wrong, with the figure, month and what you expected.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A4.6/5.0

Behavior5/5

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

With no annotations at all, the description carries the full burden and does so: it discloses the rate limit (10 reports/day per caller), where the data goes (stored for operator review, never shown to other users), the return value (a report id), and size caps (2,000 chars for message, 4 KB JSON for args). This is exactly the behavioral context the description must supply in the absence of annotations.

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 the action and the constraint, then layers on routing guidance and storage behavior with little waste. Slightly dense in one paragraph, and the character limit is repeated from the schema, but nothing is superfluous.

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?

Covers everything an agent needs for a write-side reporting tool: what to submit, limits, side effects, safety of the submitted text, return value, and preconditions. The nested args object is documented in the schema, so no output schema is needed given the description names the returned report id.

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 all three parameters are already documented, including the examples and max lengths. The description restates the same constraints (2,000 characters, tool and arguments) rather than adding format or syntax detail beyond the schema, so baseline 3 applies.

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?

States a specific verb and object: report a wrong figure or data problem, with the tool/args of the offending call. This is unmistakably a write-side feedback tool, clearly distinct from the retrieval siblings like get_series or get_catalog.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-not ('not for questions or feature requests') and a prerequisite check ('only after checking the figure'), plus a routing hint to consult get_catalog or an answer's notes first because gaps and non-comparable periods are often documented there. An agent has no ambiguity about whether to call this.

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

All TradeStats - customs trade statistics 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?