Skip to main content
Glama

Lilambd Data for Agents

budget-inflation

How do households in these countries split their budget, and how much inflation do food and energy add?. For 1-5 countries: household budget shares by COICOP group (OECD national accounts), latest food / energy / headline CPI inflation (World Bank) and the percentage-point contribution of food and household energy given each country's budget weights. Computed by Lilambd. Routes: /answer (countries*); /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": "budget-inflation"
  }
}

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.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the important behaviors — a paid call at $0.5 USDC via x402 with the _meta["x402/payment"] key, the free 3-row sample preview, and the upstream data sources — but says nothing about error handling, rate limits, or what happens if a country code is invalid.

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?

Three dense sentences: use case, returned data, then routing/payment. Nearly every clause carries information. Minor deduction for the awkward leading question with a stray '?.' and for cramming pricing into the same sentence as routing.

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?

With no output schema and a nested `params` object, the description does the necessary work by naming the returned fields, the data sources, the country range, and the payment/sample mechanics. What it leaves out — response shape details and pagination for /countries — is modest rather than critical.

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%, so the baseline would be 3, but the description goes beyond the schema by enumerating the actual route values and which parameter each route expects ('countries*' vs 'limit'), which the schema's placeholder text does not resolve. Nested `params` contents remain only loosely illustrated.

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 names the specific outputs: household budget shares by COICOP group from OECD national accounts, latest food/energy/headline CPI from the World Bank, and the percentage-point contribution of food and household energy weighted by budget shares. That is far more specific than a generic 'inflation tool', though it opens with a rhetorical question rather than a clean verb+resource statement.

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 supplies two real constraints: 'For 1-5 countries' and the route mapping ('/answer (countries*)', '/countries (limit)'), plus a free sample option. It does not say when to prefer this over siblings such as jp-household or exposure, so selection guidance is only implied by the topic.

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