Skip to main content
Glama

Lilambd Data for Agents

power-fuel-exposure

How is a country's power capacity split by fuel, and how exposed is it to current coal, gas and oil price moves?. Aggregates the WRI Global Power Plant Database for one country (capacity mix, fossil vs low-carbon share, MW per million people, oldest/largest plants) and joins World Bank Pink Sheet fuel benchmarks and the country's energy CPI to give a capacity-weighted fuel price change. 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": "power-fuel-exposure"
  }
}

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

A4.2/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 paid model ('$0.5 USDC per call via x402', _meta["x402/payment"]), the free sample escape hatch, the data provenance, and what is computed (capacity-weighted fuel price change). It stops short of rate limits, failure modes, or whether repeated calls are cached/billed separately.

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?

Front-loaded with the end-user question, then the method, then routes, then cost — a sensible order with no filler sentences. It is dense to the point of being slightly compressed (the 'country*' argument is never spelled out as a param key), which keeps it just below top marks.

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 paid aggregation tool with no output schema, the description does the necessary work: it lists the returned metrics (capacity mix, fossil vs low-carbon share, MW per million people, oldest/largest plants, weighted price change) and the billing mechanics. The only gap is how the required country value is supplied via the nested params object.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning the schema does not: it maps each route to its accepted arguments ('/answer (country*, limit)' vs '/countries (limit)'), which the generic schema text ('e.g. /search or /HND') fails to do, and it clarifies that sample=true yields a 3-row preview rather than a filtered result.

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 question the tool answers ('how is a country's power capacity split by fuel, and how exposed is it to coal, gas and oil price moves') and then names the exact sources joined (WRI Global Power Plant Database, World Bank Pink Sheet benchmarks, energy CPI). That is far more than a restatement of the name and lets an agent distinguish it from generic siblings like 'power' or 'world-power'.

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?

Usage is only implied: the routes line ('/answer (country*, limit); /countries (limit)') tells an agent which route to pick and what each accepts, and sample=true is flagged as a free preview. However, there is no explicit statement of when to use this tool versus the sibling 'exposure' or 'world-power' tools, and no stated exclusions or prerequisites beyond the payment requirement.

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