Skip to main content
Glama

Entso E

by io.github.pipeworx-io

Cross Border Flow

cross_border_flow
Read-onlyIdempotent

Physical flow across an interconnector (in_area → out_area).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
area_toYesDestination area EIC code
area_fromYesSource area EIC code
period_endYes
period_startYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesQuery parameters sent to ENTSO-E API
time_seriesYesArray of cross-border flow time series
time_series_countYesNumber of time series returned

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "area_from": "10YDE-VE-------2",
-    "area_to": "10YFR-RTE------C",
-    "period_end": "202401012300",
-    "period_start": "202401010000"
-  },
-  {
-    "area_from": "10YGB-NGET-----L",
-    "area_to": "10YNL----------L",
-    "period_end": "202412312300",
-    "period_start": "202412010000"
-  }
-]New value: +[
+  {
+    "area_from": "10YDE-VE-------2",
+    "area_to": "10YFR-RTE------C",
+    "period_end": "202504012300",
+    "period_start": "202504010000"
+  },
+  {
+    "area_from": "10YGB-NGET-----L",
+    "area_to": "10YNL----------L",
+    "period_end": "202412312300",
+    "period_start": "202412010000"
+  }
+]
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "area_from": "10YDE-VE-------2",
+    "area_to": "10YFR-RTE------C",
+    "period_end": "202401012300",
+    "period_start": "202401010000"
+  },
+  {
+    "area_from": "10YGB-NGET-----L",
+    "area_to": "10YNL----------L",
+    "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 cross-border flow time series",
+      "items": {
+        "properties": {
+          "business_type": {
+            "description": "Business type classification",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "in_domain": {
+            "description": "Destination area EIC code",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "mrid": {
+            "description": "Market Resource ID",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "out_domain": {
+            "description": "Source area EIC code",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "periods": {
+            "description": "Time periods with flow data",
+            "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": "Flow data points",
+                  "items": {
+                    "properties": {
+                      "position": {
+                        "description": "Position/index in period",
+                        "type": "number"
+                      },
+                      "value": {
+                        "description": "Physical flow in MW",
+                        "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

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, etc. Description only adds directionality (in_area → out_area), which is partially inferable from parameter names. No details on data format, time resolution, or edge cases.

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?

Extremely brief (one sentence). Not wasteful, but lacks substance. Could fit more useful information without becoming verbose.

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?

Despite rich annotations and presence of output schema, the description omits critical details about time period format, data units, or constraints. Agent may struggle to invoke correctly without additional schema inspection.

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 50% (period_start and period_end have no descriptions). The tool description does not clarify parameter formats or semantics. Examples in schema help but are not in the description.

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?

Description clearly states the tool returns physical flow across an interconnector with direction (in_area → out_area). The verb is implied by 'flow' in context of a data tool, and it distinguishes from energy-related siblings by focusing on cross-border interconnector flow.

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. No mention of prerequisites or exclusions. Agent has no context for selection beyond the description.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.1/5.0
Disambiguation2/5

Several tools have overlapping or duplicate roles: ask_pipeworx and ask_pipeworx_beta are explicitly identical right now, and deep_research/ask_pipeworx/discover_tools/suggest_questions all serve query routing. The five ENTSO-E tools are distinct but are lost among the unrelated Pipeworx/prediction-market tooling.

Naming Consistency2/5

Naming mixes single verbs (remember, forget, subscribe), noun phrases (actual_load, entity_profile), verb_noun patterns (compare_entities, discover_tools), and brand-prefixed groups (pipeworx_*, polymarket_*). Snake_case is consistent, but the verb style and naming logic vary widely with no discernible overall pattern.

Tool Count2/5

36 tools is too many for a server supposedly focused on ENTSO-E electricity data, especially since only 5 tools serve that domain. Even as a general data-access server, the set is heavy and includes redundant/beta variants (ask_pipeworx_beta, ask_pipeworx_grounded) that inflate the count.

Completeness1/5

The server name 'Entso E' implies electricity-market data, but only 5 of 36 tools cover generation, load, prices, capacity, and cross-border flow. Missing typical ENTSO-E operations like forecasts, balancing, or real-time grid status, while the remaining 31 tools belong to an unrelated data platform — severely incomplete for the advertised purpose.

Resources