Datos Gob Es

Datasets

datasets

Read-onlyIdempotent

Search the Spanish open data portal (datos.gob.es) catalog by keyword, theme, or both; returns paginated dataset listings with title, publisher, and download links.

Input Schema

Name	Required	Description	Default
`page`	No
`query`	No
`theme`	No
`page_size`	No

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 30, 2026

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

removedOutput schema / properties / page

Removed value: -{
-  "description": "Current page number",
-  "type": "number"
-}

removedOutput schema / properties / pageSize

Removed value: -{
-  "description": "Results per page",
-  "type": "number"
-}

addedOutput schema / properties / result

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

removedOutput schema / properties / results

Removed value: -{
-  "description": "Array of dataset results",
-  "items": {
-    "properties": {
-      "description": {
-        "description": "Dataset description",
-        "type": "string"
-      },
-      "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"
-  },
-  "type": "array"
-}

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

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "query": "population"
+  },
+  {
+    "page": 1,
+    "page_size": 20,
+    "query": "economic indicators",
+    "theme": "economia"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Search results from datos.gob.es catalog",
+  "properties": {
+    "page": {
+      "description": "Current page number",
+      "type": "number"
+    },
+    "pageSize": {
+      "description": "Results per page",
+      "type": "number"
+    },
+    "results": {
+      "description": "Array of dataset results",
+      "items": {
+        "properties": {
+          "description": {
+            "description": "Dataset description",
+            "type": "string"
+          },
+          "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"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, openWorldHint=true, destructiveHint=false). The description adds one genuine behavioral trait not in the annotations: results are paginated. It says nothing about default page size, maximum page size, total-count behavior, or rate limits, so the added value is modest.

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?

A single, front-loaded sentence with no wasted preamble; the resource and the filtering dimensions come first. Slightly dense with the parenthetical portal name and 'or both' filler, but efficient overall.

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 need not explain return values (its mention of title/publisher/download links is redundant but harmless). However, with 0% schema coverage on four parameters and no sibling differentiation against 'dataset', the definition leaves real gaps an agent must guess around.

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 description coverage is 0%, so the description must carry the burden. It does name two of the four parameters conceptually (keyword -> query, theme) and hints at pagination (page/page_size), but it never distinguishes page from page_size, gives no defaults or limits, and leaves the semantics of page_size entirely unstated.

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?

Specifies a concrete verb and resource: 'Search the Spanish open data portal (datos.gob.es) catalog by keyword, theme, or both'. That is enough to distinguish it from generic tools, but it never distinguishes itself from the close sibling 'dataset' (singular), which an agent could easily confuse with this catalog search.

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 only implied: searching by keyword/theme tells the agent when this tool is applicable, but there is no explicit when-to-use statement and no mention of alternatives such as 'dataset', 'themes', or 'publishers'. The agent must infer routing on its own.

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.