Skip to main content
Glama

Datos Gob Es

by io.github.pipeworx-io
OverviewDiscussionsAdmin

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

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoDataset identifier
themeNoDataset theme category
titleNoDataset title
issuedNoPublication date
modifiedNoLast modification date
publisherNoPublisher name
descriptionNoDataset description
distributionsNoAvailable data distributions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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"
+}
  2. First observed

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, and non-destructive. The description adds that it returns specific fields (title, description, publisher, etc.) and the origin (datos.gob.es), but does not disclose additional behavioral traits like authentication or rate limits. Since annotations cover safety, a score of 3 is appropriate.

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 a single sentence that is well-structured and front-loaded with the verb and resource. Every part adds value without extra words.

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?

For a simple single-fetch tool with 1 parameter, annotations, and an output schema, the description adequately explains what it does and what it returns. It covers the necessary information but could mention error handling or authentication briefly.

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 0%, so the description bears the burden of explaining the 'id' parameter. It only says 'by its ID' and provides no details on format, examples (though schema has an example), or constraints. This is insufficient for low coverage.

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 verb 'Fetch' and the resource 'full metadata for a single datos.gob.es dataset by its ID'. It also lists specific returned fields, distinguishing it from sibling tools like 'datasets' which likely return lists.

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?

The description implies use when you have a dataset ID and need full metadata, but does not explicitly state when not to use it or compare with sibling tools such as 'datasets', 'themes', or 'publishers'. No exclusions mentioned.

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 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.

Resources