Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Buscar boletines zonales de infoMIES

search_infomies_boletines_zonales
Read-only

Find infoMIES zonal bulletins by zone or consolidated yearly files, returning download links for 2017-2026 data.

Instructions

infoMIES zonal bulletins: modo="zonal" (per-zone .rar, 2017-2021, needs zona) or "consolidado" (yearly XLSX 2021-2026, still updated). Returns links.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
anioNoSpecific year to fetch.
modoNo"zonal" or "consolidado".zonal
zonaNoRequired for modo="zonal": one of "zona-1-bz".."zona-9-bz".
queryNoFree text matched (accent-insensitive) against the file's label, year, or 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. Changed5 schema fields changedv0.10.0
    • addedInput schema / properties / anio / description
      Added value: +"Specific year to fetch."
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / modo / description
      Added value: +"\"zonal\" or \"consolidado\"."
    • addedInput schema / properties / query / description
      Added value: +"Free text matched (accent-insensitive) against the file's label, year, or URL."
    • addedInput schema / properties / zona / description
      Added value: +"Required for modo=\"zonal\": one of \"zona-1-bz\"..\"zona-9-bz\"."
  3. Changed7 schema fields changedv0.8.14
    • removedInput schema / properties / anio / title
      Removed value: -"Anio"
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / modo / title
      Removed value: -"Modo"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / properties / zona / title
      Removed value: -"Zona"
    • removedInput schema / title
      Removed value: -"search_infomies_boletines_zonalesArguments"
    • removedOutput schema / title
      Removed value: -"search_infomies_boletines_zonalesDictOutput"
  4. First observedv0.8.12

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish readOnly/openWorld/non-destructive, so the bar is lower; the description adds genuinely useful traits beyond them — the archive format per mode, the per-year file cadence, and that the consolidado series is still being updated. It omits auth/rate-limit behavior and the download-vs-metadata distinction, but 'Returns links' clarifies the output nature.

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 dense sentence, front-loaded with the resource name, that conveys modes, formats, date ranges, and the zona requirement with zero 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?

With no output schema, 'Returns links' correctly sets expectations, and both modes plus their coverage windows are documented. Minor gaps remain around the default text vs json format and result volume/pagination, but nothing critical to calling the tool is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description goes further by explaining that zonal mode yields per-zone .rar files requiring zona and that consolidado yields yearly XLSX, giving semantic meaning to the modo enum beyond the schema's bare '"zonal" or "consolidado"'. It says nothing extra about anio, query, or format.

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 the specific resource (infoMIES zonal bulletins) and enumerates both retrieval modes with their deliverable formats (.rar per zone vs yearly XLSX), so an agent knows exactly what it fetches. It does not, however, distinguish itself from the sibling search_infomies_bases_mensuales, which is the nearest alternative.

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

Usage Guidelines4/5

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

The description implicitly routes mode selection by pairing each option with its coverage window (zonal 2017-2021, consolidado 2021-2026 and still updated) and states that zona is needed only for zonal. There is no explicit when-not or named alternative, but the context needed to pick a mode is present.

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