Skip to main content
Glama

usda_psd_get_world_data

Read-onlyIdempotent

Retrieve world-total USDA PSD supply and distribution forecasts for one commodity and market year, returning per-attribute values with units and PSD release vintage.

Instructions

PSD supply and distribution forecasts for one commodity and market year, world total.

One record per attribute, aggregated by PSD over every applicable country (country_code "00"). attribute_id and unit_id are PSD's integer ids, which enums.AttributeId and enums.UnitId name; value is in that unit. meta.vintage is the PSD release that last revised the figures, as upstream names it ("2026-10"), the latest release of any country for this commodity and market year (in the whole answers recorded on 2026-10-23, commit 07b88ad); meta.published_at stays empty, since PSD gives no day. The code and the year are checked before any call; a market year without data raises NotFoundError.

Args: commodity_code: PSD commodity code, seven digits, e.g. "0410000" (Wheat), "0440000" (Corn), "2222000" (Oilseed, Soybean). market_year: PSD market year, e.g. 2023; data goes back to 1960 for most commodities.

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": {
      "commodity_code": "<commodity_code>",
      "market_year": "<market_year>"
    },
    "name": "usda_psd_get_world_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
market_yearYes
commodity_codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond readOnly/idempotent/openWorld annotations, the description discloses record granularity, metadata semantics for meta.vintage, why meta.published_at is empty, validation before calling, and that a market year without data raises NotFoundError. This adds substantial behavioral context beyond what the structured annotations provide.

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 front-loaded with a clear purpose statement and then a structured Args section. It is mostly efficient, though the parenthetical about answers recorded on 2026-10-23, commit 07b88ad is development-oriented and less likely to earn its place for an agent selecting or invoking the tool.

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?

There is no output schema, but the description explains the record structure, metadata fields, validation behavior, and error handling sufficiently for correct invocation. Combined with annotations covering safety and idempotency, the definition is complete for a read-only, two-parameter PSD world-total tool.

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?

Schema description coverage is 0%, so the description must carry parameter meaning. It fully specifies commodity_code as a seven-digit PSD code with concrete examples, and explains market_year as an integer PSD market year with examples and historical depth back to 1960 for most commodities.

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—PSD supply and distribution forecasts—and states the exact scope: one commodity, one market year, world total. It further clarifies that records are aggregated over all applicable countries with country_code "00", which distinguishes it from country-level PSD siblings.

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?

The scope implies when this tool is appropriate: world-total forecasts for a single commodity and market year. However, it does not explicitly name alternatives such as country-level PSD data or time-series tools, nor does it state when not to use this tool, even though siblings like usda_psd_get_data exist.

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