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

Datos.gob.es-MCP

by AnCode666
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_latest_datasets

Fetch recently published public datasets from the Spanish Government Open Data Portal. Use a limit parameter to control the number of results.

Instructions

Get the most recently published datasets.

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": "get_latest_datasets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description must disclose behavior. It does not explain how 'most recently published' is determined, ordering, pagination, or any side effects. The description is too minimal for a tool with no safety profile.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise with no wasted words, but it lacks structure such as headings or separate sections. For a simple tool, it is adequate but could benefit from additional context without becoming verbose.

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 the single parameter and no output schema, the description fails to explain the return format, ordering criteria, or any implicit limits. It is insufficient for an agent to fully understand the tool's output and behavior.

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

Parameters3/5

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

The description adds meaning to the 'limit' parameter by stating it is the maximum number to return, which supplements the schema's default value. However, schema description coverage is 0%, so the description partially compensates but does not fully explain all aspects.

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 retrieves the most recently published datasets, using a specific verb+resource combination. However, it does not differentiate from sibling tools like list_datasets or search_datasets, which may also return dataset lists.

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 instead of alternatives (e.g., list_datasets, search_datasets). The description lacks context for selection criteria.

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