Skip to main content
Glama

SpotVahti

Compare electricity contracts in Finland

compare_electricity_contracts
Read-onlyIdempotent

Ranks Finnish household electricity contracts (spot/pörssisähkö, fixed-price and hybrid = fixed price ± monthly usage effect) by estimated yearly cost for a given consumption. Spot contracts are priced with realized hourly Nord Pool prices weighted by a typical consumption pattern. Returns the cheapest contracts with margin or energy price, monthly fee, intro offers, price check date and data source. Without postal_code only contracts sold in the whole country are included. Prices exclude grid transmission and electricity tax.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of contracts to return.
languageNoLanguage for texts and links: fi (Finnish), sv (Swedish) or en (English). Use the user's language.
home_typeNoTypical Finnish home type; sets the consumption pattern and default yearly kWh (apartment 2000, terraced_house 5000, detached_house 6000, ground_source_heat_pump 10000, direct_electric_heating 18000).
annual_kwhNoYearly electricity consumption in kWh. If omitted, the home_type default is used.
postal_codeNoFinnish postal code. Adds local contracts that are only sold in that area.
contract_typeNoFilter by contract type.any
ev_annual_kwhNoExtra yearly kWh for electric car charging at night.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description still adds real substance: how spot contracts are priced from realized hourly Nord Pool prices weighted by a typical consumption pattern, that only nationwide contracts appear when postal_code is omitted, and that prices exclude transmission and electricity tax. It does not mention pagination or ordering ties, but the priced-mechanics disclosure is well beyond the annotation bar.

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?

Front-loaded with the action, followed by methodology, then return fields, then price caveats — each sentence carries distinct information with no padding. Parenthetical definitions of pörssisähkö and hybrid are compact and load-bearing.

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

Completeness4/5

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

With no output schema, the description does the work of listing returned fields (margin/energy price, monthly fee, intro offers, price check date, data source), which is exactly what an agent needs. All parameters are optional and well documented in the schema, so the only minor gap is nothing about ordering ties or how spot estimates are dated.

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 the baseline is 3, but the description adds meaning the schema does not: the consequence of omitting postal_code (only nationally sold contracts) and that consumption drives the cost estimate. It also glosses hybrid pricing, which no single parameter field explains.

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?

Opens with a specific verb and resource ('Ranks Finnish household electricity contracts') and defines the three contract types it covers, including how hybrid is defined. An agent can immediately tell this is a cost-ranking search tool, distinct from siblings like get_contract or get_network_fees.

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 implied by 'by estimated yearly cost for a given consumption' and the postal_code scoping rule, but there is no explicit when-to-use or when-not guidance and no named alternative for related needs (e.g. get_network_fees for the excluded transmission costs). The exclusion note ('Prices exclude grid transmission and electricity tax') usefully steers follow-up questions elsewhere.

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.