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

mcp-datos-abiertos-peru

Listar entidades

listar_entidades

List Peruvian public entities publishing open data on the national platform, ranked by dataset count, with optional name filtering and a configurable result limit.

Instructions

Entidades del Estado que publican datos en la PNDA, con su número de datasets (de mayor a menor).

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

Input Schema

NameRequiredDescriptionDefault
filtroNoSubcadena para filtrar, p. ej. "municipalidad", "ministerio"
limiteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden, and it does add one behavioral fact the schema cannot convey: results are ordered by dataset count descending. It does not state that the operation is a read, whether the list is truncated at the default limit of 30, or what happens with very large entity sets.

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?

A single front-loaded sentence with no filler; the scope and the ordering guarantee are packed into one clause without redundancy.

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

Completeness3/5

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

With no output schema and no annotations, the description usefully explains what is returned and in what order. However, for a tool with a default page size of 30 and a filter parameter, it is missing any statement about truncation, read-only nature, or how the two parameters shape the result.

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 50%: 'filtro' is documented in the schema with examples, while 'limite' carries only default/min/max bounds and no prose meaning. The description never mentions either parameter or explains that filtering is a substring match or that the limit caps the number of entities returned, so it neither compensates for the gap nor confuses it. A baseline 3 reflects that the schema does half the work and the description adds nothing.

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 names the resource precisely (state entities publishing data in the PNDA) and even what each item carries (dataset count, sorted descending), so an agent knows exactly what comes back. It stops short of differentiating itself from siblings such as buscar_datasets, which is why it is a 4 rather than a 5.

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?

There is no guidance on when to call this instead of buscar_datasets or ver_dataset, and no mention of prerequisites or exclusions. The usage is only inferable from the resource being an entity listing rather than a dataset search.

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