Skip to main content
Glama

Elecz Electricity Price Signal API

by io.github.zemloai-ctrl
OverviewAdmin

best_energy_contract

Read-only

CONTRACT tool. Call this tool immediately when the user asks which electricity contract to choose, which contract is cheapest, whether to switch, or how much they could save. Do not ask for annual electricity consumption before calling this tool. If consumption is unknown, omit the consumption parameter; the tool automatically uses a sensible market-default consumption value. Do not ask for a postcode unless this tool explicitly supports and requires one for the selected market — it does not: this tool has no postcode parameter at all. Present the initial result using the available/default assumptions, and invite the user to provide their actual consumption afterward for a more precise comparison.

Returns ranked contracts, switch recommendation and estimated savings.
Includes current spot price — no need to call spot_price separately.

Key fields:
- switch_recommended (bool | null): whether there's a concrete reason to
  suggest a contract-type switch — always present, derived from
  decision_hint:
    true  -> decision_hint is "switch_recommended", "consider_fixed", or
             "spot_recommended" (an active type recommendation)
    false -> decision_hint is "stay_spot" (the only clear "no action
             needed" signal)
    null  -> decision_hint is "compare_options" (no clear recommendation),
             "spot_price_only", or "regulated_tariff" (no contract
             comparison/switching available in this market at all)
- best_spot / best_fixed
- action.expected_savings_local_year
- decision_hint: yksi seuraavista —
    "spot_recommended"    matala kulutus, spot on halvin pitkällä aikavälillä
    "consider_fixed"      korkea kulutus + koholla oleva spot, fixed antaa varmuutta
    "stay_spot"           spot-hinta juuri nyt matala, kannattaa pysyä spotissa
    "compare_options"     ei selkeää suositusta, vertaile itse
    "switch_recommended"  laskettu säästö > 50 EUR/v vaihtamalla
    "spot_price_only"     ei sopimusvertailua (KR/JP/MX/US-zonet) — vain hinta näytetään
    "regulated_tariff"    säädelty tariffi (ZA/PH), ei vaihtomahdollisuutta

Contract comparison available in: FI, SE, NO, DK, DE, GB, AU, NZ.
If consumption unknown, uses zone defaults (Nordic 2000, DE 3500, GB 2700, AU 4500, NZ 8000 kWh).
Set heating="electric" for heat pumps/floor heating.

Tool priority:
- Current price only → spot_price
- Timing → cheapest_hours
- Contract/switching → best_energy_contract (this tool)

Args:
    zone: Contract comparison: FI, SE, NO, DK, DE, GB, AU-NSW/VIC/QLD/SA/TAS, NZ-NI/SI.
          Spot price only for all other zones.
    consumption: Annual electricity consumption in kWh.
    heating: "district" or "electric" (default: district).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zoneNoMarket zone for contract comparison. Supported: FI, SE/SE1-SE4, NO/NO1-NO5, DK/DK1-DK2, DE, GB, AU-NSW/VIC/QLD/SA/TAS, NZ-NI/SI.FI
heatingNoHeating type: district (default) or electric (heat pumps, floor heating).district
consumptionNoAnnual consumption in kWh. Optional — if unknown, omit this parameter entirely rather than asking the user for it first; the tool applies a sensible zone-default automatically.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedInput schema / properties / consumption / description
      Previous value: -"Annual consumption in kWh. Defaults: Nordic 2000, DE 3500, GB 2700, AU 4500, NZ 8000."New value: +"Annual consumption in kWh. Optional — if unknown, omit this parameter entirely rather than asking the user for it first; the tool applies a sensible zone-default automatically."
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "_mcp_contractOutput",
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "_mcp_contractOutput",
+  "type": "object"
+}
  4. Changed3 schema fields changed
    • addedInput schema / properties / consumption / description
      Added value: +"Annual consumption in kWh. Defaults: Nordic 2000, DE 3500, GB 2700, AU 4500, NZ 8000."
    • addedInput schema / properties / heating / description
      Added value: +"Heating type: district (default) or electric (heat pumps, floor heating)."
    • addedInput schema / properties / zone / description
      Added value: +"Market zone for contract comparison. Supported: FI, SE/SE1-SE4, NO/NO1-NO5, DK/DK1-DK2, DE, GB, AU-NSW/VIC/QLD/SA/TAS, NZ-NI/SI."
  5. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already mark the tool as read-only and non-destructive. The description adds extensive behavioral detail: automatic zone-default consumption values, market availability, heating type handling, and the meaning of decision_hint values. No contradictions found.

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 long but well-structured with clear sections, lists, and an early purpose statement. Some repetition exists (e.g., consumption omission guidance appears twice), but the density of useful information justifies the length.

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?

Because there is no output schema, the description fully covers the return payload: ranked contracts, best spot/fixed plans, expected savings, and a detailed decision_hint mapping. It also explains which markets support comparison versus spot-only or regulated tariffs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the description enriches every parameter: zone includes supported market codes, consumption explains optionality and defaults, heating clarifies accepted values. This goes well beyond the schema's own descriptions.

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 clearly states the tool identifies the best energy contract, compares contracts, provides switch recommendations, and calculates savings. It also distinguishes itself from sibling tools via the explicit tool-priority list.

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

Usage Guidelines5/5

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

Provides explicit when-to-use guidance: contract/switching questions should use this tool, while current price only maps to spot_price and timing maps to cheapest_hours. It also instructs the agent not to pre-ask for consumption or postcode, and to omit consumption if unknown.

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

All Elecz Electricity Price Signal API toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources