Kyrodata — Brazil Trade, Crop & Commodity Data

Supply and demand balance sheet

kyrodata_get_supply_demand_balance

Read-onlyIdempotent

Published supply and demand balance (physical, in tonnes) for one agricultural hub, season by season: production, imports, exports, consumption, initial and final stock, whether the season is still an estimate, and how many months a partial season measures. hub accepts only the hubs that have a published balance sheet, which is fewer than the hubs the forecast tools cover; closedOnly drops the current season, which is a projection and still moves. The source is a Brazilian government body and is named in the result. This is the physical BALANCE of a season. The price verdict for the same hub is kyrodata_get_hub_summary, and the weather risk behind production is kyrodata_get_climate_reading. Credit class: level (any level tool in a 60-second session = 2 credits; a session is capped at 3).

Input Schema

TableJSON Schema

Name	Required	Description
`hub`	Yes	Which commodity hub to read. Only hubs with a published balance sheet appear here.
`closedOnly`	No	Restrict to seasons already closed. The current season is a projection and still moves.
`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.

Changed3 schema fields changedSep 7, 2026

addedInput schema / properties / closedOnly / description

Added value: +"Restrict to seasons already closed. The current season is a projection and still moves."

addedInput schema / properties / hub / description

Added value: +"Which commodity hub to read. Only hubs with a published balance sheet appear here."

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?

The description states the data is published, identifies it as a balance sheet, clarifies the current season is a projection that 'still moves,' names the data source, and notes credit cost and session cap. Annotations declare read-only and idempotent, and the description adds context about changing projections without contradicting the hints.

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?

The description is dense but every sentence serves a purpose: data type, units, temporal behavior, source, credit cost, and sibling differentiators. It front-loads the core purpose before adding constraints and alternatives. No filler or repetition.

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 input restrictions (published hubs only), parameter semantics (closedOnly meaning), data domain (physical, seasonal), source attribution, output nuance (estimate vs closed), and how siblings differ. Combined with 100% schema coverage and output schema, the agent has everything to select and invoke the 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 coverage is 100%, and the description reinforces important parameter semantics: hub is restricted to published balance sheets, and closedOnly excludes the projection. It also clarifies how response_format maps to result size. The description does not restate parameter names but provides valuable context beyond the schema.

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 clearly states this returns a published supply and demand balance sheet in physical tonnes, for one agricultural hub, by season. It enumerates the exact contents (production, imports, exports, etc.) and distinguishes itself from the related price and weather tools.

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 says when to use this tool versus get_hub_summary (price verdict) and get_climate_reading (weather risk). It also clarifies which hubs are valid, the meaning of `closedOnly`, and the special projection status of the current season.

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?