Skip to main content
Glama

World food prices: FAO Food Price Index (monthly)

get_food_prices
Read-only

Free. FAO Food Price Index as published by the UN Food and Agriculture Organization: latest month, value (2014-2016 = 100), change vs previous month and vs a year earlier, the five sub-indices (meat, dairy, cereals, vegetable oils, sugar) and the last 13 months. International commodity prices, not shop prices; recent months get revised.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_food_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only cover readOnlyHint and openWorldHint; the description adds genuinely useful behavior beyond them — the data is free, sourced from the UN FAO, measured on a fixed 2014-2016=100 base, and 'recent months get revised,' which tells the agent the latest figures are provisional. It stops short of stating refresh cadence or exactly how far back revisions typically go.

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?

Two sentences, front-loaded with the cost and the resource name, then a compact enumeration of returned fields followed by the two scoping caveats. No filler and no repetition of the title.

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 no output schema and zero parameters, the description carries the full burden of explaining return values, and it does so precisely — fields, units/base year, history depth, and revision behavior. Nothing an agent needs in order to call or interpret this tool is missing.

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?

The tool takes no parameters, so there is no schema semantics to add and the baseline applies. The description correctly spends its words on output content rather than inventing parameter guidance.

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 resource (FAO Food Price Index) with its publisher, and enumerates exactly what is returned: latest month, index value on a 2014-2016=100 base, month-over-month and year-over-year change, the five sub-indices, and a 13-month history. The clause 'International commodity prices, not shop prices' draws a clean boundary that separates it from a generic prices tool.

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 'not shop prices' note gives implicit guidance about which questions this tool answers, but there is no explicit when-to-use statement and no named alternative (e.g. get_prices) with the condition that would select it. An agent must infer routing from the data description alone.

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.