Skip to main content
Glama

Lilambd Data for Agents

staple-price-shock

How exposed is a country's diet to the current world price of its main staple?. Joins FAOSTAT food balance (calories, top staple, cereal self-sufficiency) with the World Bank Pink Sheet price of that staple (latest month, y/y, 5y, 12-month range) and the country's food CPI, plus a computed exposure flag. Computed by Lilambd. Routes: /answer (country*, limit); /countries (limit). Paid $0.5 USDC per call via x402 (_meta["x402/payment"]); set sample=true for a free 3-row preview.

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": {
      "route": "<route>"
    },
    "name": "staple-price-shock"
  }
}

Input Schema

NameRequiredDescriptionDefault
routeYesOne of: /answer, /countries. Replace {placeholders} with a value, e.g. /search or /HND.
paramsNoQuery parameters, e.g. {"q":"tokyo","limit":"50"}
sampleNoFree preview, max 3 rows

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does substantial work: it discloses the price ($0.5 USDC per call), the payment mechanism (x402 via _meta["x402/payment"]), a free 3-row preview escape hatch, and the freshness windows of the underlying data. What is missing is any statement about rate limits, failure/refund behavior on a paid call, or what the computed exposure flag's values mean.

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 question is front-loaded in the first sentence, followed by data provenance, then routes, then payment — a sensible priority order. It is dense but nearly every clause carries information; only the 'Computed by Lilambd' attribution and the unreconciled '/search' example spend words without helping invocation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter tool with a nested params object and no output schema, the definition tells the agent what the response is composed of (calories, top staple, self-sufficiency, price deltas, range, CPI, exposure flag), which substitutes for a return description. Gaps remain around valid values for limit, what countries are accepted (ISO codes?), and payment failure handling, but nothing essential for a first correct call is absent.

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%, so the schema already documents route, params, and sample, making 3 the baseline. The description adds real value by enumerating the two valid route values and by revealing the meaningful query keys (country with an asterisk, limit) inside the otherwise unconstrained params object. The asterisk convention for 'required' is never explained, and the '/HND' example is not tied to a named parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a concrete analytical question — how exposed a country's diet is to the world price of its main staple — and names the exact data joins (FAOSTAT food balance for calories/top staple/cereal self-sufficiency, World Bank Pink Sheet price for latest month, y/y, 5y, 12-month range, plus food CPI and an exposure flag). That is far more specific than a restated name. It stops short of naming a sibling it is not, so an agent must infer the boundary versus tools like exposure or real-commodity-price.

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?

It gives routing guidance (use /answer with a country, or /countries to enumerate) and a cost-avoidance path via sample=true, which is genuine when-to-use help. However there is no explicit statement of when to prefer this over the similarly named exposure or price-check siblings, and the schema example '/search' does not match either listed route, which could confuse route selection.

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