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

Datos.gob.es-MCP

by AnCode666
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_publisher_datasets

Retrieve datasets published by any organization on datos.gob.es by providing the publisher's URI. Optionally limit the number returned.

Instructions

Get datasets published by a specific organization.

Args: publisher_uri: URI of the publisher 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": {
      "publisher_uri": "<publisher_uri>"
    },
    "name": "get_publisher_datasets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
publisher_uriYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It does not state whether the tool is read-only, what side effects exist, or how it handles pagination, errors, or large results. The mention of 'limit' implies some control but lacks explanation of behavior beyond defaults.

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 yet informative, with a clear one-sentence purpose followed by parameter documentation. Every sentence is necessary and front-loaded, making it easy for an agent to parse quickly.

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?

With no output schema, the description should at least hint at the return format (e.g., list of dataset objects). It does not describe the output structure, pagination behavior, or any side effects. Given the tool's relative simplicity, the description is incomplete for an agent to fully understand what it returns.

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%, but the description adds meaning for both parameters: 'publisher_uri' as 'URI of the publisher' and 'limit' as 'Maximum number of datasets to return (default: 10)'. This compensates for the missing schema descriptions, though it could provide more detail on URI format or constraints.

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 action ('Get datasets') and the filtering criterion ('published by a specific organization'), which is distinct from sibling tools like list_datasets and search_datasets. The verb 'Get' and resource 'datasets' are specific and unambiguous.

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?

There is no guidance on when to use this tool versus alternatives (e.g., search_datasets, list_datasets). The description does not mention when not to use it or provide context for choosing this tool over siblings.

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