Skip to main content
Glama
eu-nordic-open-data-mcp

eu-nordic-open-data-mcp

Any Fingrid CC BY dataset

fingrid_dataset

Fetch raw Fingrid time series for specified dataset IDs and recent hour windows, using curated CC BY dataset IDs for grid data analysis.

Instructions

Raw time series for given Fingrid dataset ids (Fingrid-produced CC BY datasets only). Curated ids: 51, 52, 74, 75, 106, 124, 165, 166, 177, 181, 188, 191, 192, 193, 194, 209, 244, 245, 247, 248, 277, 283, 317, 318, 319, 329, 330, 336, 395, 396, 397.

Input Schema

NameRequiredDescriptionDefault
hoursBackNo
datasetIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden. It says the data is 'raw' and limited to CC BY datasets, but gives no information on resolution, units, pagination, rate limits, or licensing attribution requirements attached to the results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is tight and front-loaded, but the bulk of the text is an unstructured id dump with no indication of what each id represents, which makes it hard to skim and only partly earns its space.

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

Completeness2/5

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

With no annotations, no output schema, and no schema descriptions, the description should explain the time window behavior and dataset semantics. It leaves the agent guessing about the default 24h window, maximum 168h, and what each id returns.

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

Parameters2/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, but it never explains datasetIds (array of 1-20 integers) or hoursBack (default 24, max 168). The curated id list helps with datasetIds values but gives no meaning to the ids or the time window.

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 states a specific verb and resource ('raw time series for given Fingrid dataset ids') and scopes it to Fingrid-produced CC BY datasets. It does not, however, distinguish this from the sibling fingrid_series, which an agent could easily confuse with it.

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?

There is no statement of when to use this tool rather than fingrid_series, fingrid_grid_snapshot, or fingrid_cheap_hours. The curated id list implies usage but never says 'use this when you need arbitrary/raw series' or names any alternative.

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