Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Ver archivos de una publicación del INEC

get_inec_publicacion_archivos
Read-only

Retrieve download links (PDF, XLSX, CSV, ZIP) for a specific INEC publication by its id or URL, so you can access the original source files directly.

Instructions

File links (PDF/XLSX/CSV/ZIP) in one INEC publication (id or URL from search_inec_publicaciones).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
postYesEither the numeric "id" from search_inec_publicaciones, or the publication's full ecuadorencifras.gob.ec URL.
formatNotext summary (default) or json structured result.text

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. Changed2 schema fields changedv0.10.0
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / post / description
      Added value: +"Either the numeric \"id\" from search_inec_publicaciones, or the publication's full ecuadorencifras.gob.ec URL."
  3. Changed4 schema fields changedv0.8.14
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / post / title
      Removed value: -"Post"
    • removedInput schema / title
      Removed value: -"get_inec_publicacion_archivosArguments"
    • removedOutput schema / title
      Removed value: -"get_inec_publicacion_archivosDictOutput"
  4. First observedv0.8.12

TDQS

A3.6/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, covering the safety profile. The description adds that the output is file links restricted to one publication, but omits any pagination, rate-limit, or empty-result behavior. Given annotation coverage, a 3 is appropriate.

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 tightly-worded sentence that front-loads what is returned (file links) and their types. No filler.

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 simple two-parameter read tool with no output schema, the description conveys the input source (search_inec_publicaciones) and the nature of the result (file links with formats). It is adequate, though it could better disambiguate from get_inec_estadistica_files.

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% and the schema already documents both 'post' (id or URL) and 'format' (text/json enum with default). The description only echoes the 'id or URL' notion and adds no format or syntax detail beyond the schema, so the baseline 3 holds.

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: retrieving file links (PDF/XLSX/CSV/ZIP) within a single INEC publication. It names the parent search tool, but does not differentiate itself from the very similar sibling get_inec_estadistica_files, so an agent could confuse the two.

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 '(id or URL from search_inec_publicaciones)' implies the workflow of searching first to obtain the post id/URL, giving implicit usage context. There is no explicit statement of when to prefer this tool over siblings or when not to use it.

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