Datos Gob Es

Dataset

dataset

Read-onlyIdempotent

Fetch full metadata for a single datos.gob.es dataset by its ID; returns title, description, publisher, themes, distribution URLs, and license.

Input Schema

Name	Required	Description	Default
`id`	Yes

Output Schema

Name	Required	Description	Default
`format`	No
`result`	No
`version`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedSep 30, 2026

removedOutput schema / properties / description

Removed value: -{
-  "description": "Dataset description",
-  "type": "string"
-}

removedOutput schema / properties / distributions

Removed value: -{
-  "description": "Available data distributions",
-  "items": {
-    "properties": {
-      "accessUrl": {
-        "description": "URL to access the distribution",
-        "type": "string"
-      },
-      "format": {
-        "description": "Data format (CSV, JSON, etc.)",
-        "type": "string"
-      },
-      "id": {
-        "description": "Distribution identifier",
-        "type": "string"
-      },
-      "title": {
-        "description": "Distribution title",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "type": "array"
-}

addedOutput schema / properties / format
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / id

Removed value: -{
-  "description": "Dataset identifier",
-  "type": "string"
-}

removedOutput schema / properties / issued

Removed value: -{
-  "description": "Publication date",
-  "type": "string"
-}

removedOutput schema / properties / modified

Removed value: -{
-  "description": "Last modification date",
-  "type": "string"
-}

removedOutput schema / properties / publisher

Removed value: -{
-  "description": "Publisher name",
-  "type": "string"
-}

addedOutput schema / properties / result

Added value: +{
+  "properties": {
+    "_about": {
+      "type": "string"
+    },
+    "definition": {
+      "type": "string"
+    },
+    "extendedMetadataVersion": {
+      "type": "string"
+    },
+    "first": {
+      "type": "string"
+    },
+    "hasPart": {
+      "type": "string"
+    },
+    "isPartOf": {
+      "type": "string"
+    },
+    "items": {
+      "items": {},
+      "type": "array"
+    },
+    "itemsPerPage": {
+      "type": "number"
+    },
+    "page": {
+      "type": "number"
+    },
+    "startIndex": {
+      "type": "number"
+    },
+    "type": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

removedOutput schema / properties / theme

Removed value: -{
-  "description": "Dataset theme category",
-  "type": "string"
-}

removedOutput schema / properties / title

Removed value: -{
-  "description": "Dataset title",
-  "type": "string"
-}

addedOutput schema / properties / version
```
Added value: +{
+  "type": "string"
+}
```

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "id": "padron-municipal"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Single dataset details from datos.gob.es",
+  "properties": {
+    "description": {
+      "description": "Dataset description",
+      "type": "string"
+    },
+    "distributions": {
+      "description": "Available data distributions",
+      "items": {
+        "properties": {
+          "accessUrl": {
+            "description": "URL to access the distribution",
+            "type": "string"
+          },
+          "format": {
+            "description": "Data format (CSV, JSON, etc.)",
+            "type": "string"
+          },
+          "id": {
+            "description": "Distribution identifier",
+            "type": "string"
+          },
+          "title": {
+            "description": "Distribution title",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "id": {
+      "description": "Dataset identifier",
+      "type": "string"
+    },
+    "issued": {
+      "description": "Publication date",
+      "type": "string"
+    },
+    "modified": {
+      "description": "Last modification date",
+      "type": "string"
+    },
+    "publisher": {
+      "description": "Publisher name",
+      "type": "string"
+    },
+    "theme": {
+      "description": "Dataset theme category",
+      "type": "string"
+    },
+    "title": {
+      "description": "Dataset title",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive behavior, so safety is fully covered without the description. The description adds only the set of returned fields, which duplicates the output schema, and omits error behavior (unknown ID), rate limits, or auth needs. Adds some value but nothing beyond structured fields.

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?

One front-loaded sentence that leads with the verb and resource. Slightly wasteful in enumerating return fields that the output schema already covers, but otherwise tight with no filler.

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 a single-parameter read tool with full annotation coverage and an existing output schema, the description supplies what an agent needs to select and call it. Only error/edge-case behavior (invalid or missing ID) is unaddressed.

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?

Single `id` parameter with 0% schema description coverage; the description only says 'by its ID', which adds no format, source, or example semantics beyond the schema's own example. With one parameter this is a small gap, but the description still fails to characterize what kind of ID is valid.

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 ('Fetch'), resource ('full metadata'), scope ('a single datos.gob.es dataset'), and selector ('by its ID'). The singular 'dataset'/'single dataset' framing cleanly distinguishes it from the sibling plural `datasets`, which reads as a list/search tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the singular-vs-plural sibling naming and by the required ID, but the description never says when to use this instead of `datasets`, `search_within`, or `themes`, nor what happens on an unknown ID. Adequate inference, no explicit guidance.

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

All Datos Gob Es tools Inspect

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.