Skip to main content
Glama
Sign In

Entso E

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Day Ahead Prices

day_ahead_prices
Read-onlyIdempotent

Day-ahead auction prices (€/MWh) per hour for a bidding zone. Period is YYYYMMDDHHmm format (UTC).

Input Schema

NameRequiredDescriptionDefault
areaYesBidding-zone EIC code (e.g. "10YDE-VE-------2" Germany)
period_endYesYYYYMMDDHHmm (UTC)
period_startYesYYYYMMDDHHmm (UTC)

Output Schema

NameRequiredDescriptionDefault
queryYesQuery parameters sent to ENTSO-E API
time_seriesYesArray of time series data
time_series_countYesNumber of time series returned

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "area": "10YDE-VE-------2",
-    "period_end": "202401012300",
-    "period_start": "202401010000"
-  },
-  {
-    "area": "10YFR-RTE------C",
-    "period_end": "202412312300",
-    "period_start": "202412010000"
-  }
-]New value: +[
+  {
+    "area": "10YDE-VE-------2",
+    "period_end": "202504012300",
+    "period_start": "202504010000"
+  },
+  {
+    "area": "10YFR-RTE------C",
+    "period_end": "202412312300",
+    "period_start": "202412010000"
+  }
+]
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "area": "10YDE-VE-------2",
+    "period_end": "202401012300",
+    "period_start": "202401010000"
+  },
+  {
+    "area": "10YFR-RTE------C",
+    "period_end": "202412312300",
+    "period_start": "202412010000"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "query": {
+      "description": "Query parameters sent to ENTSO-E API",
+      "type": "object"
+    },
+    "time_series": {
+      "description": "Array of time series data",
+      "items": {
+        "properties": {
+          "business_type": {
+            "description": "Business type classification",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "in_domain": {
+            "description": "Inbound domain EIC code",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "mrid": {
+            "description": "Market Resource ID",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "out_domain": {
+            "description": "Outbound domain EIC code",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "periods": {
+            "description": "Time periods with data points",
+            "items": {
+              "properties": {
+                "period_end": {
+                  "description": "Period end timestamp (ISO 8601)",
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "period_start": {
+                  "description": "Period start timestamp (ISO 8601)",
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "points": {
+                  "description": "Data points with position and value",
+                  "items": {
+                    "properties": {
+                      "position": {
+                        "description": "Position/index in period",
+                        "type": "number"
+                      },
+                      "value": {
+                        "description": "Price (€/MWh) or quantity value",
+                        "type": "number"
+                      }
+                    },
+                    "required": [
+                      "position",
+                      "value"
+                    ],
+                    "type": "object"
+                  },
+                  "type": "array"
+                },
+                "resolution": {
+                  "description": "Time resolution (e.g., PT60M for hourly)",
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "psr_type": {
+            "description": "Production source resource type",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "time_series_count": {
+      "description": "Number of time series returned",
+      "type": "number"
+    }
+  },
+  "required": [
+    "query",
+    "time_series_count",
+    "time_series"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds context about hourly granularity and the specific data type (day-ahead auction prices), which is useful beyond the annotations.

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?

The description is extremely concise, only two sentences, with the key information front-loaded. Every word adds value without redundancy.

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?

Given the tool's simplicity and the presence of an output schema, the description covers the essential aspects: what data is returned, the unit, the time format, and the zone concept. It is nearly complete for a straightforward fetch operation.

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 coverage is 100%, so the schema itself documents all three parameters. The description reinforces the format and adds 'bidding zone' context, which is already in the schema, providing marginal additional value.

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 tool provides day-ahead auction prices per hour for a bidding zone, with units and format specified. This distinguishes it from sibling tools like actual_generation_per_type or actual_load.

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?

No guidance on when to use this tool versus alternatives. The description does not mention conditions, exclusions, or comparisons with other energy tools.

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

All Entso E 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