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

mcp-datos-abiertos-peru

Actualizar catálogo

actualizar_catalogo

Refresh the cached catalog index from Peru's National Open Data Platform (PNDA), useful only when you need dataset listings updated immediately instead of waiting for the automatic 24-hour renewal.

Instructions

Vuelve a descargar el índice del catálogo desde la PNDA (normalmente no es necesario: se renueva cada 24 h).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/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 discloses the source (PNDA) and the implicit auto-refresh cadence, but says nothing about whether the re-download blocks, how long it takes, whether it replaces existing cached data, or what permissions/credentials are needed for the external fetch.

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?

One sentence, front-loaded with the action and followed by the caveat that prevents unnecessary calls. No filler or redundancy.

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?

For a zero-parameter maintenance/refresh tool, the description covers what it does and when to avoid it. The remaining gap is the outcome of the call (return value or failure behavior), which no output schema documents.

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 tool takes zero parameters, so there is no parameter meaning to add; the baseline of 4 applies. The description correctly implies the operation is unconditional and needs no input.

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: 'Vuelve a descargar el índice del catálogo desde la PNDA' tells the agent this refreshes the catalog index from an external source. It is clearly distinguishable from the read-oriented siblings (buscar_datasets, ver_dataset), though it does not name them.

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 parenthetical '(normalmente no es necesario: se renueva cada 24 h)' gives a concrete when-not-to-use condition and the reason behind it. It stops short of naming which sibling to use instead when the agent only wants to read catalog data.

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