UK Data for Agents

eu_household_electricity_price

Read-onlyIdempotent

Average household electricity price per kWh in one European country, every half-year, for a typical home using 2,500-5,000 kWh a year, with all taxes included by default. Answers "how much does electricity cost in Germany per kWh" or "where is power cheapest in Europe". Source: Eurostat dataset nrg_pc_204. Averages across tariffs, so a given contract can be higher or lower; published with a lag of a few months. (cost: 1 credit)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "eu_household_electricity_price"
  }
}

Input Schema

Name	Required	Description
`n`	No	integer, optional, most recent half-years, 1-100, default 4
`geo`	No	string, required, 2-letter Eurostat country code (DE, FR, ES, IT, NL, PL, EL = Greece) or country name; EU27_2020, EA (euro area), EA21, EA20 also accepted. EU, EFTA and EU candidate countries only (no UK)
`tax`	No	string, optional: 'I_TAX' all taxes and levies included (default), 'X_TAX' excluding taxes, 'X_VAT' excluding VAT

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description earns credit for what they cannot say: results are tariff averages so an individual contract may differ, data is published with a multi-month lag, taxes are included by default, and the call costs 1 credit. Return shape is not described, but no output schema exists and the caveats cover the main behavioral risks.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Roughly ninety words, front-loaded with the metric and its scope, then the routing examples, then source and caveats. Every sentence carries information an agent would otherwise have to guess; nothing is padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-metric statistical lookup with fully documented parameters and no output schema, the description supplies scope, defaults, caveats, provenance and cost. An agent can decide to call it and interpret the result without further context.

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 baseline is 3, but the description adds real meaning: the half-year cadence explains what the 'n' most-recent-periods parameter counts, and 'all taxes included by default' explains the default state of the tax parameter. It does not restate the geo code list, which the schema already handles well.

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 names a specific metric, unit (per kWh), geography (one European country), granularity (every half-year) and population (households using 2,500-5,000 kWh/yr). This clearly separates it from siblings such as eu_house_price_growth, eu_inflation_rate or trade_tariff without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Two concrete example questions ('how much does electricity cost in Germany per kWh', 'where is power cheapest in Europe') anchor when to reach for it, and the schema's geo note scopes it to EU/EFTA/candidate countries with no UK. No explicit when-not-to-use or named alternative tool is given, so it falls short of a 5.

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

All UK 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?