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

Datos.gob.es-MCP

by AnCode666
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_publishers

List the organizations that publish datasets on the Spanish Government Open Data Portal. Adjust the number of results with the limit parameter.

Instructions

List publishers (organizations) that publish datasets.

Args: limit: Maximum number of publishers 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_publishers"
  }
}

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?

No annotations are provided, so the description carries full burden. It only mentions the limit parameter but does not disclose behavior like pagination, sorting, maximum limit, or whether it returns all publishers or only a subset. The description is minimally informative beyond the schema.

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 with only two sentences, no unnecessary words or repetition. It efficiently states the purpose and explains the single parameter.

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?

Given no output schema, the description fails to explain what the return value contains (e.g., list of publisher names or details). It also lacks context about the default behavior beyond the parameter default. Incomplete for an agent to understand the full effect.

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?

The description adds meaning to the 'limit' parameter beyond the schema's type and default, explaining it as the maximum number of publishers to return. With schema coverage at 0%, this extra detail is valuable, though it is brief.

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 that the tool lists publishers (organizations) that publish datasets. This is a specific verb and resource, and it distinguishes itself from sibling tools like 'get_publisher_datasets' which retrieves datasets for a given publisher.

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 is provided on when to use this tool versus alternatives. There is no mention of prerequisites, context, or when not to use it.

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