Skip to main content
Glama

Nordic Financial MCP

by io.github.AIDataNordic
OverviewDiscussionsAdmin

get_current_power_price

Read-only

Fetch today's hourly day-ahead electricity spot prices for a Nordic bidding zone.

Use this for current and near-term (today/tomorrow) price queries. Do not use for historical price analysis — use search_filings with report_type='macro_summary' and a date reference in the query for that purpose. Tomorrow's prices are published by NordPool around 13:00 CET; requests before that time will return "not yet available" for the tomorrow field.

All zones return prices in EUR/kWh (NordPool day-ahead, native currency). Norwegian zones (NO1–NO5) use hvakosterstrommen.no; all other zones use ENTSO-E.

Args: zone: Bidding zone code. Options: NO1 (East/Oslo), NO2 (Southwest), NO3 (Central/Trondheim), NO4 (North), NO5 (West/Bergen), SE1–SE4, DK1, DK2, FI. include_tomorrow: Set to True to also fetch tomorrow's hourly prices if already published (default False).

Returns: Dict containing zone, date, current_hour_utc, current price, and a 'today' summary with min/max/avg and the full hourly list. Includes a 'tomorrow' key if include_tomorrow=True. Returns {'error': ''} if price data is unavailable for the requested zone or date.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zoneNoBidding zone: NO1–NO5, SE1–SE4, DK1, DK2, or FINO1
include_tomorrowNoAlso fetch tomorrow's prices if available (published after 13:00 CET)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / include_tomorrow / description
      Added value: +"Also fetch tomorrow's prices if available (published after 13:00 CET)"
    • addedInput schema / properties / zone / description
      Added value: +"Bidding zone: NO1–NO5, SE1–SE4, DK1, DK2, or FI"
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Describes price units (EUR/kWh), data sources (hvakosterstrommen.no vs ENTSO-E), and behavior for unavailable tomorrow data. Annotations already declare readOnlyHint and openWorldHint; description adds valuable transparent context without contradiction.

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?

Well-structured with clear sections (purpose, usage, parameters, returns). Front-loaded with main verb and resource. Slightly verbose in parameter listing but justified by tool complexity; no redundant sentences.

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?

Covers all aspects: purpose, usage constraints, behavioral details, parameter options, return format, and error handling. With only 2 parameters and detailed annotations, the description is fully adequate for an agent to invoke the tool correctly.

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 100%, so baseline is 3. The description repeats parameter details and adds minor behavioral context (sources, timing) but does not fundamentally enhance understanding beyond the schema.

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 verb 'Fetch' and the resource 'today's hourly day-ahead electricity spot prices for a Nordic bidding zone'. It distinguishes from sibling tool search_filings for historical analysis, making the purpose specific and unambiguous.

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?

Explicitly says 'Use this for current and near-term (today/tomorrow) price queries. Do not use for historical price analysis — use search_filings...' and provides timing details (publication at 13:00 CET). This offers clear when-to-use and when-not-to-use guidance.

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

All Nordic Financial MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources