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

mcp-datos-abiertos-peru

Previsualizar recurso CSV

previsualizar_recurso

Preview the first rows and columns of a CSV resource, including inferred data types and sample values, so you can confirm exact column names before running queries.

Instructions

Lee solo el inicio de un recurso CSV y devuelve sus columnas (con tipo inferido y ejemplo) y las primeras filas. Úsalo SIEMPRE antes de consultar_recurso para conocer los nombres exactos de las columnas.

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

Input Schema

NameRequiredDescriptionDefault
urlNoURL directa del recurso, si no se tiene el id
filasNo
recurso_idNo`id` del recurso (de ver_dataset). Preferido.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the load and does disclose key traits: it is a partial read (only the start of the resource) and what is returned (column types inferred, sample values). It omits failure behavior for non-CSV or invalid resources and any size/auth considerations, leaving some gaps.

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 sentences, tightly structured: the return contract first, the usage rule second. Every clause carries information and nothing is redundant.

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?

No output schema exists, yet the description adequately specifies the return shape (columns with type and example, plus first rows). The main residual gap is how to choose between url and recurso_id, which the agent must read from the schema.

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 coverage is 67% and the description never mentions url, recurso_id, or filas; "las primeras filas" only loosely gestures at the filas parameter. The schema's "Preferido" note on recurso_id does the differentiation work instead of the description, which is baseline-adequate but adds little.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and scope ("Lee solo el inicio de un recurso CSV") and the exact return payload: columnas with inferred type and example, plus primeras filas. This makes it clearly distinguishable from consultar_recurso, which reads the full resource.

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

Usage Guidelines5/5

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

Gives an explicit pre-condition with emphasis ("Úsalo SIEMPRE antes de consultar_recurso") and names the sibling that follows it, so an agent knows both the ordering and the alternative. No when-not guidance is given, but the sequencing rule is unambiguous.

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