Skip to main content
Glama
mcp-datos-abiertos-peru

mcp-datos-abiertos-peru

Buscar datasets

buscar_datasets

Search Peru's National Open Data Platform by free text to find relevant datasets and return dataset names for subsequent metadata and resource review.

Instructions

Busca datasets en la Plataforma Nacional de Datos Abiertos del Perú por texto libre (ranking BM25 sobre título, entidad, etiquetas y descripción). Úsalo primero para encontrar qué datos existen. Devuelve el nombre de cada dataset, que luego se pasa a ver_dataset.

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": {
      "consulta": "<consulta>"
    },
    "name": "buscar_datasets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limiteNo
entidadNoFiltra por entidad publicadora (subcadena), p. ej. "MINSA", "MEF", "INEI"
formatoNoSolo datasets con un recurso de este formato, p. ej. "csv"
consultaYesTexto libre, p. ej. "fallecidos covid", "ejecución presupuestal municipal"
modificado_desdeNoFecha ISO mínima de última actualización, p. ej. "2025-01-01"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It usefully discloses the ranking method and its fields plus the shape of the return value, but says nothing about pagination/limite behavior, how entidad and formato filters interact with ranking, or what happens when no results match.

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?

Two tight sentences with no filler: the search scope and ranking are front-loaded, then the workflow purpose and output handoff. Every clause contributes information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description correctly fills that gap by stating it returns the `nombre` of each dataset. For a five-parameter search tool the definition is largely sufficient, with only the filter/ranking interaction and result-limit behavior left implicit.

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?

Schema description coverage is 80%, so the schema already documents consulta, entidad, formato, and modificado_desde with examples. The description only restates that search is free text, adding no syntax or semantic detail beyond what the schema provides; baseline 3 applies.

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?

States a specific verb and resource ("Busca datasets"), names the exact platform, and explains the retrieval mechanism (BM25 over título, entidad, etiquetas y descripción). It positions itself as the discovery entry point feeding into ver_dataset, which gives enough contrast with that sibling, though other siblings (listar_entidades, consultar_recurso) are not addressed.

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?

"Úsalo primero para encontrar qué datos existen" gives clear when-to-use guidance — it is the first-step discovery tool. The follow-up routing to ver_dataset clarifies the workflow, but there is no explicit statement of when NOT to use it (e.g., when the dataset name is already known).

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