Skip to main content
Glama
Sign In
Datos.gob.es-MCP

Datos.gob.es-MCP

by AnCode666
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_datasets

Retrieve a list of public datasets from the Spanish government open data portal, with an optional limit on the number of results.

Instructions

List datasets available in the Spanish Government Open Data Portal.

Args: limit: Maximum number of datasets to return (default: 10)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_datasets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It only states it 'list datasets,' implying a read operation, but omits behavioral details like pagination, ordering, result format, or whether it returns all datasets or a subset. The limit parameter hints at truncation but no further disclosure.

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 extremely concise: two sentences plus an argument definition. The first sentence states the core purpose. No unnecessary words.

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?

For a listing tool, important context is missing: pagination details (offset, cursor), ordering, total count, and whether results are stable. The single parameter is explained but overall completeness is low given no output schema and minimal behavioral disclosure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% (no parameter descriptions in schema). The description compensates by explaining 'limit: Maximum number of datasets to return (default: 10),' adding clear meaning beyond the schema's type and default values.

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?

The description clearly states the tool lists datasets from the Spanish Government Open Data Portal. It distinguishes from siblings like get_dataset_details (single dataset) and search_datasets (filtered search), but could be more explicit about the scope (e.g., 'all datasets' vs 'latest').

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 provided on when to use this tool versus alternatives like search_datasets or get_latest_datasets. The description lacks explicit when-to-use/when-not-to-use context.

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

Deploy Server

Other Tools