Kyrodata — Brazil Trade, Crop & Commodity Data

Run one of the catalog reports

kyrodata_run_report

Read-onlyIdempotent

Runs one of the product's pre-built catalogue reports by id and returns its rows, up to 50. reportId is an enum of the catalogue's ids, so the whole catalogue travels in this schema and no lookup call is needed; params carries the values the chosen report declares, and columnIds narrows the projection — omitted, the report's default columns come back, and the columns that identify each row are included either way. Columns locked behind a paid plan are declared, with a header stating what an upgrade unlocks, while their values stay out. Rows count against the account's export quota. This serves a report that already exists as a product. An ad-hoc question about trade is kyrodata_compare_trade or kyrodata_list_trade_series, and a citable public document is kyrodata_fetch. Credit class: comex (up to 2 comex tools per 60-second session = 1 credit).

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum rows to return.
`params`	No	Values for the parameters the chosen report declares.
`reportId`	Yes	Which catalogue report to run, by id. Each report declares its own parameters, which go in `params`.
`columnIds`	No	Only these columns, by id. Omit for the report’s default set; the columns that identify a row are always returned.
`response_format`	No	How much of the answer to return. `concise` (the default) carries the headline figures; `detailed` adds the row-level series behind them and counts against the export quota.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Raw numbers behind the text.
`memo`	Yes	true = identical call in the last 10 min, served again: 0 credits.
`rows`	No	Table rows; detailed only, capped per tool.
`error`	No	Failure message when status = error.
`links`	Yes	screen = product page with these numbers.
`denied`	No	When status = denied: reason, feature, upgradeUrl.
`status`	Yes	ok = data; denied = plan; error = failure or timeout.
`window`	No	Like-for-like window: from, to (YYYY-MM), label, months, crossesSeason.
`caveats`	Yes	Reading caveats.
`credits`	Yes	charged, balance (null = unlimited), resetAt, session {charged, endsAt} of the 60-s billing session.
`sources`	Yes	Per source: label, nameable, asOf.
`dataVersion`	Yes	Identity of the data that answered.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 10, 2026

changedInput schema / properties / reportId / description

Previous value: -"Which catalogue report to run. Call the tool with no arguments to list the reports and the parameters each one takes."New value: +"Which catalogue report to run, by id. Each report declares its own parameters, which go in `params`."

addedInput schema / properties / reportId / enum

Added value: +[
+  "comex.exports.1",
+  "comex.imports.1",
+  "comex.partners.1",
+  "comex.opportunities.1",
+  "comex.series.1",
+  "comex.elasticities.1",
+  "comex.heading.partners.1",
+  "comex.country.basket.1",
+  "hub.trade.flow.1",
+  "hub.trade.flow.2",
+  "hub.production.regions.1",
+  "hub.production.regions.2",
+  "hub.balance.sheet.1",
+  "hub.climate.regions.1",
+  "costs.survey.1",
+  "climate.history.1"
+]

Changed5 schema fields changedSep 7, 2026

addedInput schema / properties / columnIds / description

Added value: +"Only these columns, by id. Omit for the report’s default set; the columns that identify a row are always returned."

addedInput schema / properties / limit / description
```
Added value: +"Maximum rows to return."
```

addedInput schema / properties / params / description

Added value: +"Values for the parameters the chosen report declares."

addedInput schema / properties / reportId / description

Added value: +"Which catalogue report to run. Call the tool with no arguments to list the reports and the parameters each one takes."

addedInput schema / properties / response_format / description

Added value: +"How much of the answer to return. `concise` (the default) carries the headline figures; `detailed` adds the row-level series behind them and counts against the export quota."

First observedSep 6, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint), the description discloses concrete behavioral traits: the 50-row cap, the projection behavior for locked paid-plan columns (headers returned, values withheld), the export-quota accounting, and the credit-class rate limit. These are material operational details an agent needs and are not present in the annotations or schema.

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?

The description is dense and front-loaded, with the core action in the first sentence and behavior details following logically. It is longer than average because it covers many nuances (locked columns, quota, credit, alternatives), and nearly every sentence earns its place. The phrase 'This serves a report that already exists as a product' is slightly redundant with the opening, but it does set up the contrast with alternatives.

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?

For a tool with 5 parameters, a 16-value enum, nested objects, quotas, and credit accounting, the description covers all the essential operational context: how reportId is self-contained, how params and columnIds interact, default-column behavior, locked-column handling, export quota, and credit class. The output schema exists, so return-value details are appropriately left to the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema description coverage is 100%, the description adds meaningful semantics: it explains why no lookup call is needed (the reportId enum carries the whole catalogue), how params relates to the chosen report's declared parameters, and exactly how columnIds behaves when omitted or provided. This goes well beyond the baseline of restating schema text.

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 opens with a specific verb and resource: 'Runs one of the product's pre-built catalogue reports by id and returns its rows'. It clearly identifies the tool's scope (pre-built reports) and immediately distinguishes it from ad-hoc tools like kyrodata_compare_trade and kyrodata_list_trade_series. The purpose is unmistakable even without reading the schema.

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?

The description explicitly states when this tool is appropriate ('serves a report that already exists as a product') and names precise alternatives for other cases: 'An ad-hoc question about trade is kyrodata_compare_trade or kyrodata_list_trade_series, and a citable public document is kyrodata_fetch.' No inference is required to decide between this and its siblings.

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

All Kyrodata — Brazil Trade, Crop & Commodity 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?