Skip to main content
Glama

Primary Source Commodities

Farm-Gate Prices for Several Crops

producer.prices.bundle
Read-onlyIdempotent

FAOSTAT farm-gate producer prices by country for up to 20 crops in ONE call. A separate tool from producer.prices, for the same pricing reason as price.bundle. This is what a grower was paid at the farm gate — NOT an export unit value and NOT the benchmark price.latest returns; all three are correct and differ. Paid; charged only if at least one crop resolves.

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

Input Schema

NameRequiredDescriptionDefault
yearNoYear to summarise. Defaults to the latest stored.
codesYesCrop instrument codes, up to 20. Example: ["CC", "KC"].

Output Schema

NameRequiredDescriptionDefault
countYes
commoditiesYes
dropped_codesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world behavior, so the description's added value is the billing/cost model: 'Paid; charged only if at least one crop resolves.' That is genuinely useful context an agent cannot get from annotations. It does not discuss empty results for unresolvable codes or ordering, which keeps it below a 5.

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?

Dense and front-loaded: scope first, sibling relationship second, disambiguation and cost last. The phrase 'for the same pricing reason as price.bundle' is somewhat indirect and assumes familiarity with another tool, costing a bit of clarity.

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?

With only two parameters, full schema coverage, an output schema, and complete annotations, the description covers everything an agent needs: data provenance (farm-gate, FAOSTAT), the batch limit, competing alternatives, and the cost condition. Nothing material is missing.

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 coverage is 100% and both parameters are documented with defaults and examples, so the baseline is 3. The description's only addition is reiterating the 'up to 20 crops' bound, which the schema already states; it adds no new meaning about code formats or year semantics.

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 statement ('FAOSTAT farm-gate producer prices by country for up to 20 crops in ONE call') and explicitly positions itself against siblings: 'A separate tool from producer.prices'. It also rules out two confusable data sources (export unit value and price.latest benchmarks), so an agent can identify it 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 Guidelines4/5

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

It names the sibling producer.prices and signals the batch rationale ('up to 20 crops in ONE call' / 'price.bundle'), plus explicit exclusions versus price.latest and export unit values. It stops short of stating outright 'use this instead of producer.prices when you need more than one crop', leaving the selection rule partially implicit.

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