Skip to main content
Glama

Primary Source Commodities

Producer Prices by Country

producer.prices
Read-onlyIdempotent

Farm-gate producer prices by country for one commodity and year, from FAOSTAT. Use for 'where is this cheap at source' and for comparing what growers are actually paid across countries. THIS IS NOT A BENCHMARK: a producer price is what the farmer received, and differs from price.latest and from the export unit value in trade.partners — all three can be correct and several-fold apart. Covers seven crops only (ZC ZW ZS ZR KC CC CT); sugar, palm and livestock are deliberately unmapped because FAOSTAT prices a different product for those. Annual, usually one to two years behind.

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": "<commodity>"
    },
    "name": "producer.prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoFour-digit year; defaults to the latest available.
commodityYesInstrument code. Example: KC for coffee.

Output Schema

NameRequiredDescriptionDefault
yearYes
notesYesRead before presenting any figure from this tool.
sourceNo
commodityYes
countriesYesCountries, cheapest first
license_tagNo
faostat_itemNoThe FAOSTAT item actually priced
country_countNo
years_availableNo
peer_band_multipleNoThe multiple of the median beyond which far_from_peers is set
vs_median_availableNoFalse when too few countries report for a median to mean anything
peer_median_usd_per_tonneNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description nonetheless adds real behavioral context beyond that: annual cadence, a one-to-two-year publication lag, a seven-crop coverage ceiling, and the warning that the series can be several-fold apart from sibling price measures. These additions are useful but the description stops short of describing return shape or per-country coverage gaps; with annotations carrying the safety profile, 3 is defensible.

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 core purpose is front-loaded in the first sentence, and every subsequent sentence carries distinct information: the use cases, the non-benchmark warning, the crop ceiling, and the cadence. It is dense and slightly long, but no sentence is filler; a tighter edit could fold the cadence and lag note together.

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?

Given a simple two-parameter tool with an output schema, an explicit return-value explanation is unnecessary. The description covers coverage limits, temporal resolution, data lag, and the confusable sibling series, which is everything an agent needs before calling it.

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 both parameters are already documented, so the baseline is 3. The description goes further by explaining why the commodity enum is capped at seven codes (FAOSTAT prices a different product for sugar, palm and livestock) and by framing the year as annual data typically one to two years behind, which clarifies what the 'latest available' default will actually return.

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+resource+scope: 'Farm-gate producer prices by country for one commodity and year, from FAOSTAT.' It immediately disambiguates from price.latest and the export unit value in trade.partners, so an agent can pick it out among siblings without opening a 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?

Gives an explicit use case ('where is this cheap at source', comparing grower pay across countries) plus an explicit negative: 'THIS IS NOT A BENCHMARK', naming the two alternative series it is commonly confused with. It also bounds applicability by listing the seven supported crops and stating that sugar, palm and livestock are deliberately excluded.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources