Skip to main content
Glama

SpotVahti

Finnish spot price statistics

get_spot_price_statistics
Read-onlyIdempotent

Realized Finnish day-ahead (Nord Pool) electricity spot price statistics incl. VAT: average over the last 12 months, monthly and yearly averages since 2021, and the average price for each hour of the day with the cheapest and most expensive hours. Not live prices and not a forecast.

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_spot_price_statistics"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoLanguage for texts and links: fi (Finnish), sv (Swedish) or en (English). Use the user's language.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior context beyond that: data source (Nord Pool), VAT inclusion, temporal coverage since 2021, and explicit exclusion of live/forecast data. It doesn't state freshness/last-updated or units (c/kWh vs EUR/MWh), which is the remaining gap.

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?

Two sentences, front-loaded with the resource and its contents, ending with the most decision-relevant constraint (not live, not forecast). Dense but every clause carries information; the long enumeration in sentence one is slightly heavy but not wasteful.

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 must convey what comes back, and it does so by listing each statistic produced. For a parameterless, read-only data tool this is nearly sufficient; only units of the price values and data freshness remain unstated.

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?

There is a single optional language parameter with 100% schema description coverage and an enum already documented as fi/sv/en with usage guidance ('Use the user's language'). The description adds nothing about the parameter, but the schema fully carries it, so the baseline 3 applies.

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 gives a specific verb+resource (Finnish day-ahead Nord Pool spot price statistics) and enumerates the exact contents: 12-month average, monthly and yearly averages since 2021, and hour-of-day averages with cheapest/most expensive hours. It also carves out a clear boundary ('not live prices and not a forecast'), which cleanly separates it from contract/supplier/network-fee siblings.

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

Usage Guidelines4/5

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

The negation 'Not live prices and not a forecast' tells the agent when this tool is inappropriate, and the enumerated content implies when it is appropriate (historical/statistical questions). It stops short of naming an alternative tool for live prices or forecasts, so it is clear context without explicit routing.

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.