tibber-mcp-server

Get Price Forecast

get_price_forecast

Get today's and tomorrow's electricity prices with min, max, average, and cheapest interval. Choose hourly or quarter-hourly resolution.

Instructions

Preise für heute und (falls schon publiziert) morgen, jeweils mit Min/Max/Durchschnitt und günstigstem/teuerstem Intervall.

resolution: 'HOURLY' (24 Werte/Tag) oder 'QUARTER_HOURLY' (96 Werte/Tag). Die Felder heißen in beiden Rastern gleich ('hours', 'cheapest_hour') — im Viertelstundenraster meinen sie die Viertelstunde.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`home_id`	No
`resolution`	No		HOURLY

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.3.0Sep 26, 2026
- addedInput schema / properties / resolution
```
Added value: +{
+  "default": "HOURLY",
+  "type": "string"
+}
```
First observedv0.1.0Jul 29, 2026

TDQS

A3.5/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 of behavioral disclosure. It explains conditional availability ('falls schon publiziert'), what statistics are returned, and clarifies the field-name semantics across resolutions. It does not mention home_id behavior or error cases, but the main data behavior is transparent.

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?

The description is compact and well structured: three sentences, each adding necessary information. It front-loads the main result, then covers resolution options, then clarifies the field-name caveat. No filler or repetition.

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

Completeness3/5

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

Core behavior and return contents are well covered, and an output schema exists so return-structure details are not required. The main gaps are the missing meaning of 'home_id' and the lack of usage guidance relative to sibling tools, which leaves the definition slightly incomplete for an agent.

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?

The description thoroughly documents 'resolution' with its two values and value counts, and clarifies the quarter-hour meaning of fields. However, 'home_id' is not described at all, and with 0% schema coverage this leaves one parameter unexplained.

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 identifies the resource: price forecasts for today and, if published, tomorrow, with min/max/average and cheapest/most expensive interval. It is specific and understandable, though it does not explicitly differentiate itself from sibling tools like get_current_price or find_cheapest_hours.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives such as get_current_price or find_cheapest_hours. The forecast wording implies usage context, but no explicit conditions, exclusions, or alternative routing is provided.

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

Deploy Server