Skip to main content
Glama

Lilambd Data for Agents

energy-bill-hours

What does a household's yearly electricity and gas cost in an EU country, and how many hours of work pay for it?. Eurostat household electricity and gas prices (all taxes) with Europe rank and history, turned into an annual bill for your consumption and into hours of average paid work (ILOSTAT hourly earnings). Computed by Lilambd. Routes: /answer (country*, kwh, gj, 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": "energy-bill-hours"
  }
}

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.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 behavioral burden and does well by disclosing the data sources, paid access cost of $0.5 USDC per call, x402 payment mechanism, and free sample preview. It still does not describe error behavior or full response structure beyond the conceptual annual bill and hours-of-work output.

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 description is front-loaded with the core question and then supplies data sources, routes, payment, and sample details in a compact structure. It is dense but purposeful, with only minor attribution text that is less useful for tool selection.

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 tool with nested parameters, no output schema, and no annotations, the description is fairly complete: it explains the output concept, data sources, route options, payment requirement, and free preview. It could still be improved with more explicit route selection guidance and response limitations.

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 is 3, but the description adds meaningful route-specific parameter semantics by listing /answer (country*, kwh, gj, limit) and /countries (limit). This goes beyond the generic route/params schema by clarifying which parameters belong to which 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?

The description clearly states a specific purpose: computing yearly EU household electricity and gas costs and converting them into hours of work. It is much more than a restatement of the name, but it does not explicitly differentiate itself from potentially related siblings such as prices or wage-hours.

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 route list gives implied usage: /answer for country-level calculations and /countries for listing available countries. However, there is no explicit when-to-use guidance, no exclusions, and no comparison to sibling tools.

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