Lilambd Data for Agents

world-power

World Power: country electricity profile. One call returns a country's electricity in numbers: generation by fuel (TWh) and shares for 2025 (or 2024), change vs the previous year, fossil and low-carbon share, carbon intensity (gCO2e/kWh), demand, net imports, power-sector emissions, installed plant capacity by fuel and the five largest plants. 214 countries plus World and regions. Values as published by Ember, the Energy Institute and WRI; nothing estimated. Routes: /; /mix (country*, year); /answer (country*, year); /countries (limit, offset). 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": "world-power"
  }
}

Input Schema

Name	Required	Description
`route`	Yes	One of: /, /mix, /answer, /countries. Replace {placeholders} with a value, e.g. /search or /HND.
`params`	No	Query parameters, e.g. {"q":"tokyo","limit":"50"}
`sample`	No	Free preview, max 3 rows

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A3.7/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, that values are as-published from Ember, Energy Institute and WRI with nothing estimated, and the 2025/2024 vintaging. It stops short of describing failure modes or what the root '/' route returns.

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?

It is front-loaded with the purpose, then the payload, then provenance, then routes and pricing – a logical order. The metric enumeration is dense but each item is information an agent needs to judge relevance; only the source list borders on surplus.

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, so the description must carry the return shape, and it does by enumerating the metrics and units (TWh, gCO2e/kWh). Payment mechanics and the free preview are covered. Slight gaps remain on pagination behavior for /countries and on error responses for paid calls.

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 baseline is 3, but here the description genuinely earns more by mapping each route to its query params and marking required ones with an asterisk, which the generic schema text ('One of: /, /mix, /answer, /countries') does not. The params object is still only illustrated by example, not enumerated per route.

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?

"Country electricity profile" plus an enumeration of the returned metrics (generation by fuel, carbon intensity, demand, net imports, capacity, largest plants) gives a concrete verb-plus-resource picture. Coverage (214 countries plus World and regions) further pins scope. It does not explicitly differentiate itself from the sibling tool named 'power', which leaves a small ambiguity.

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 description provides intra-tool routing guidance by naming each route and its parameters (/mix, /answer take country* and year; /countries takes limit and offset), and it explains the free sample=true preview path. It gives no explicit when-to-use/when-not guidance versus the 'power' sibling, so selection between the two remains inferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Lilambd Data for Agents tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?