Skip to main content
Glama

Data Europa

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Groups

groups
Read-onlyIdempotent

List thematic dataset categories (groups) on the EU open-data portal (e.g. environment, transport, economy); returns category names and IDs for use as filters in search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo
categoriesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / categories
      Added value: +{
+  "items": {
+    "properties": {
+      "id": {
+        "type": "string"
+      },
+      "label": {
+        "type": "string"
+      },
+      "resource": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / count
      Added value: +{
+  "type": "number"
+}
    • removedOutput schema / properties / data
      Removed value: -{
-  "description": "Array of groups",
-  "items": {
-    "description": "Group/category metadata",
-    "type": "object"
-  },
-  "type": "array"
-}
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 20
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "List of themes/groups/categories",
+  "properties": {
+    "data": {
+      "description": "Array of groups",
+      "items": {
+        "description": "Group/category metadata",
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds useful context about the returned content and portal scope but does not disclose operational details such as pagination, defaults, or open-world behavior.

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?

A single sentence that front-loads the action and resource, includes concrete examples, and states the downstream use case. Every element earns its place with no filler.

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?

For a low-complexity tool with one optional parameter, rich annotations, and an output schema, the description covers purpose, return content, and search integration. The only minor gap is the limit parameter, which structured data already mitigates.

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?

The schema has 0% description coverage, and the description says nothing about the limit parameter. While the name is self-explanatory, the description does not compensate for the schema gap by mentioning effect, bounds, or defaults.

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 opens with a specific verb and resource: 'List thematic dataset categories (groups) on the EU open-data portal', and further specifies the return payload (category names and IDs) and their purpose as search filters. This clearly differentiates it from sibling tools like organizations and tags.

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?

The description gives clear usage context by noting the results are 'for use as filters in search' and scopes the tool to the EU open-data portal. It does not explicitly name alternatives or state when-not-to-use, so it stops just short of full routing guidance.

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

All Data Europa 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