Skip to main content
Glama

Lilambd Data for Agents

real-commodity-price

Is a commodity really dearer now than it was in a given month, after US inflation?. Takes a World Bank Pink Sheet commodity or index and a historical month, deflates by US headline CPI and returns the old price in today's dollars, nominal and real change, nominal annualised growth and the inflation-adjusted all-time peak month. Computed by Lilambd. Routes: /items (limit); /answer (item*, month*). 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": "real-commodity-price"
  }
}

Input Schema

NameRequiredDescriptionDefault
routeYesOne of: /items, /answer. 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.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the computation source (Lilambd), the exact cost ($0.5 USDC per call via x402 in _meta["x402/payment"]) and a free 3-row preview via sample=true — payment/auth requirements are the critical risk here and they are stated. It omits error behaviour, limits on repeated calls, and permissible month formats, so it is strong but not complete.

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 opening question front-loads the value proposition and the remaining sentences are dense with substance rather than filler. Structure suffers slightly because routes, payment and the preview flag are compressed into a single run-on paragraph with asterisk shorthand, but nothing is genuinely wasted.

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?

There is no output schema, yet the description enumerates the returned fields (today's-dollar price, nominal and real change, annualised growth, peak month), and it covers cost plus a free preview path, which is what an agent needs before committing a paid call. Remaining gaps are the item-name vocabulary and month format, partially mitigated by the /items discovery route.

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%, but the schema text is largely boilerplate ('One of: /items, /answer', generic params object), so the description adds real meaning by mapping each route to its parameters (limit for /items; item plus month for /answer) and by explaining sample as a free preview cap. The terse 'item*'/'month*' shorthand and the absence of any example of a valid Pink Sheet item name leave some ambiguity.

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 framing question is followed by a precise statement of the transformation: takes a World Bank Pink Sheet commodity or index plus a historical month, deflates by US headline CPI, and returns today's-dollar price, nominal/real change, annualised growth and inflation-adjusted peak month. That is a specific verb-and-resource pair an agent can match to a request, but the description never contrasts itself with related siblings such as price-check, budget-inflation or staple-price-shock, so it stops short of full sibling differentiation.

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?

Route hints ('/items (limit)', '/answer (item*, month*)') and the sample=true free preview tell the agent how to start cheaply and which route fits listing versus answering, but there is no explicit when-to-use/when-not-to-use statement and no comparison against alternative tools in the catalog. The asterisk notation on item and month is not explained, leaving requiredness to inference.

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