Skip to main content
Glama

Gexiro DACH Pulse & Alexa Voice Suite MCP

get_epex_electricity_price

Get live and upcoming hourly EPEX Spot Day-Ahead electricity prices in Germany (ct/kWh wholesale spot and retail gross) and cheapest EV/appliance window.

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": "get_epex_electricity_price"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations and no output schema, the description carries the full burden. It does usefully disclose temporal scope ('live and upcoming hourly'), region, and both wholesale and retail price bases, plus a computed cheapest window. However, it omits timezone, update cadence, how many hours the 'cheapest window' spans, and what happens outside market publication hours.

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?

A single dense sentence with the resource and time scope front-loaded and no filler. Units and the extra cheapest-window output are packed into parentheses efficiently.

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 zero-parameter tool with no output schema or annotations, the description covers what is returned, at what granularity, in what units, for what market and country, plus the derived window output. Remaining gaps (timezone, refresh cadence) are minor and do not prevent a correct call.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The description does add useful context about what the returned figures represent (wholesale spot vs retail gross in ct/kWh), which is beyond the empty schema.

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 verb ('Get'), a specific resource ('EPEX Spot Day-Ahead electricity prices'), the geography ('Germany'), the units ('ct/kWh wholesale spot and retail gross'), and a derived extra ('cheapest EV/appliance window'). This is unmistakably distinct from price siblings like get_fuel_station_prices_de or get_heating_oil_and_pellet_price.

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 by the topic: an agent can infer it should call this when it needs German electricity spot prices or a cheap-charging window. There is no explicit when-to-use logic, no note on when the data is unavailable (e.g. weekends/holidays), and no routing to any alternative sibling.

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