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

mcp-datos-abiertos-peru

Ver dataset

ver_dataset

Retrieves complete metadata and the resource list—including ID, format, size, and URL—for a Peru open data dataset by slug or ID from the live API.

Instructions

Metadatos completos de un dataset y la lista de sus recursos (archivos) con su id, formato, tamaño y URL. Consulta la API en vivo para tener la versión más reciente.

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": {
      "nombre": "<nombre>"
    },
    "name": "ver_dataset"
  }
}

Input Schema

NameRequiredDescriptionDefault
nombreYes`nombre` (slug) o `id` del dataset, tal como lo devuelve buscar_datasets

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that it hits the live API to return the freshest version, which tells the agent results are current but implies latency/network dependence. It says nothing about authentication, rate limits, or failure behavior for an invalid slug.

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

Conciseness4/5

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

Two sentences, front-loaded with the payload and followed by the freshness note. No filler, though the second sentence is a mild aside that could be folded in.

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 compensates by enumerating the returned metadata and per-resource fields, which is the key information for this tool. Remaining gaps are edge cases (missing dataset, pagination of very large file lists) rather than core omissions.

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 single parameter has 100% schema description coverage, including the crucial note that it accepts a slug or id as returned by buscar_datasets, so the baseline is 3. The description adds no syntax, format, or disambiguation detail beyond the schema.

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?

Names a specific resource (dataset) and enumerates exactly what comes back: full metadata plus the resource/file list with id, format, size and URL. An agent can distinguish it from a search tool or a single-resource tool without opening the schema, though it never names the sibling it complements.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the returned content: use it when you need the dataset's metadata together with its file inventory. There is no explicit when-to-use statement, no guidance on preferring this over a resource-level tool, and no mention of what to do if the dataset is not found.

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