Skip to main content
Glama

entsoe-mcp

Check data coverage

data_coverage
Read-onlyIdempotent

Show what data is available and how current it is for (endpoint × zone) — call before querying if you're not sure a recent date is available yet. Each pair's newest year carries latest_data_at, its newest stored record; lag grades every pair on how old that record is.

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

Input Schema

NameRequiredDescriptionDefault
zoneNo
endpointNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 real behavioral context beyond them: each pair's newest year carries latest_data_at and a lag grade measuring record age, which tells the agent what the response encodes and how to interpret staleness.

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?

Three sentences, front-loaded with the capability and then the call-before-querying advice, with no filler. The backticked field names make the second half denser than necessary but each sentence earns its place.

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

Completeness3/5

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

An output schema exists, so the description is not obliged to spell out the return shape, though it helpfully previews latest_data_at and lag. The gap is on the input side: for a two-parameter coverage tool the agent still has to guess how zone and endpoint filter the response. Adequate but with a clear hole.

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 carry the two optional parameters, and it does not. It never says that zone and endpoint narrow the result set, nor what the null defaults mean (presumably all pairs). The '(endpoint × zone)' phrasing hints at the axes but adds no usable parameter meaning.

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?

States a specific verb+resource: it reports what data is available and how current it is, per endpoint × zone pair. That availability/freshness scope is distinct from catalog-type siblings like list_endpoints or list_zones and from data-fetching siblings like get_series, so an agent can tell what this tool answers.

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?

Gives concrete when-to-use guidance: call it before querying if unsure whether a recent date is available. That is a clear pre-flight context. It lacks any when-not guidance or named alternative, so it stops short of the top score.

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.

Resources