tibber-mcp-server

Get Current Price

get_current_price

Retrieve current electricity price with Tibber level, daily rank, and percentage deviation from average. Choose hourly or quarter-hourly resolution.

Instructions

Aktueller Strompreis mit Einordnung: Tibber-Level, Rang im Tagesverlauf und prozentuale Abweichung vom Tagesdurchschnitt.

resolution: 'HOURLY' (Stundenpreis) oder 'QUARTER_HOURLY' (Preis der laufenden Viertelstunde — seit der 15-Minuten-Abrechnung der tatsächlich gültige Preis).

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

B3.3/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It explains the behavioral distinction between HOURLY and QUARTER_HOURLY and why the latter is the actually valid price, which is valuable. However, it does not state read-only behavior, permission needs, or side effects, though these are likely implicit for a 'get' tool.

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?

Two sentences, zero filler, main purpose front-loaded, followed by the only parameter that needs clarification. Well-structured and appropriately sized.

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?

The return content is described, and an output schema exists, so return shape is covered. However, the description lacks usage guidance for choosing this tool over siblings and does not explain home_id. For a tool with only two optional parameters, it comes close but has clear gaps.

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 description coverage is 0%, so the description must compensate. The resolution parameter is well explained with both values and its semantic nuance. The home_id parameter is not mentioned at all, leaving its purpose unclear. Partial compensation only.

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 the tool returns the current electricity price with context (Tibber level, daily rank, percentage deviation). The word 'aktuell' differentiates it from forecast siblings, but it does not explicitly name them, so it's clear but relies on inference.

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?

No explicit when-to-use or when-not-to-use guidance is given. The description never mentions alternatives like get_price_forecast or find_cheapest_hours, so an agent must infer from the name that this is for current price only.

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

Deploy Server