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

Datos.gob.es-MCP

by AnCode666
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

search_datasets

Search datasets by keyword in title, description, and tags from the Spanish Government Open Data Portal. Control how many datasets are returned.

Instructions

Search datasets by keyword in title, description, and keywords/tags.

Args: keyword: Keyword to search for (case-insensitive). limit: Maximum number of datasets to return (default: 10).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "keyword": "<keyword>"
    },
    "name": "search_datasets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
keywordYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions case-insensitive search and a default limit, but does not disclose output format, pagination, error handling, or behavior with empty keyword. This is minimal 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 concise with two sentences plus parameter details. It is front-loaded and contains no redundant information.

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?

The description adequately explains the search scope and parameters, but lacks information about return values (since no output schema). Given the tool is a search, knowing what fields are returned would be helpful for completeness.

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

Parameters5/5

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

The description fully explains both parameters: keyword as a case-insensitive search term, and limit as maximum results with default 10. Since schema description coverage is 0%, the description adds all necessary meaning.

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 tool searches datasets by keyword in title, description, and keywords/tags. This distinguishes it from siblings like list_datasets (lists all) and get_dataset_details (single dataset).

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 provides clear context for when to use this tool: for keyword-based search across specific fields. It does not explicitly mention when not to use it or alternatives, but the context is sufficient given sibling tools.

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