Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Ver archivos de una página de publicaciones del BCE

get_bce_pagina_archivos
Read-only

Retrieve files from a BCE publication page using its pagina_id, returning title, URL and format, most recent first. Filter the indices catalog by year to reach older files.

Instructions

Files of one BCE publication page (pagina_id from search_bce_paginas): title, URL and format, most recent first. anio filters the indices catalog by year.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
anioNoOnly for catalogo="indices": restrict to one year (0 = all).
formatNotext summary (default) or json structured result.text
catalogoYesindices or cuentas_nacionales.
pagina_idYesThe page's `pagina_id` from search_bce_paginas.
max_archivosNoCap on returned files, 1-200 (most recent first); use anio to reach further back.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.13.0
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null
  2. Addedv0.10.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the ordering convention ('most recent first') and the catalogo-specific scope of anio, but discloses nothing about rate limits, result truncation behavior, or failure modes.

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 compact sentences, front-loaded with the resource and its return shape before the filtering note. No redundancy or filler; the telegraphic phrasing costs a little readability but not precision.

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?

With five parameters, no output schema and rich annotations, the description supplies the essential missing piece: what the call returns (title, URL, format) and in what order. The catalog dimension and the format=json option are handled by the schema, so nothing critical is left unexplained.

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 100%, so every parameter is already documented in the schema, including the anio/catalogo coupling and the max_archivos cap. The description's sentence about anio largely restates the schema, adding no new syntax or semantics. Baseline 3 applies when the schema does the heavy lifting.

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+resource: files of one BCE publication page, and even enumerates the returned fields (title, URL, format) and ordering. It names where pagina_id comes from, which separates it from the other *archivos siblings (e.g. get_inec_publicacion_archivos). It stops short of an explicit contrast with any alternative tool.

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?

The parenthetical '(pagina_id from search_bce_paginas)' implies the search-then-fetch workflow, which is useful. Beyond that there is no when-to-use/when-not guidance, no mention of when another sibling (e.g. search_bce_indicador or get_bce_iem_table) would be preferable.

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

Deploy Server

Other Tools