Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Ver documentos de una colección del IESS

get_iess_archivos
Read-only

Retrieve IESS documents from boletines, estudios actuariales, or audit reports, with direct links and optional year or text filters.

Instructions

Documents in one IESS collection with direct links. anio is required for informes_auditoria.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
anioNoFilter to one year.
queryNoFree text matched (accent-insensitive) against título (and descripción/grupo where the collection has one).
formatNotext summary (default) or json structured result.text
coleccionYes"boletines" (Boletines Estadísticos, annual, 1978- 2024 confirmed), "estudios_actuariales" (actuarial valuation studies per fund, published only for a handful…

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. Changed4 schema fields changedv0.10.0
    • addedInput schema / properties / anio / description
      Added value: +"Filter to one year."
    • addedInput schema / properties / coleccion / description
      Added value: +"\"boletines\" (Boletines Estadísticos, annual, 1978- 2024 confirmed), \"estudios_actuariales\" (actuarial valuation studies per fund, published only for a handful…"
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / query / description
      Added value: +"Free text matched (accent-insensitive) against título (and descripción/grupo where the collection has one)."
  3. Changed6 schema fields changedv0.8.14
    • removedInput schema / properties / anio / title
      Removed value: -"Anio"
    • removedInput schema / properties / coleccion / title
      Removed value: -"Coleccion"
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"get_iess_archivosArguments"
    • removedOutput schema / title
      Removed value: -"get_iess_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, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds only 'with direct links' regarding the response and the conditional anio requirement; it says nothing about result volume, pagination, or what happens for collections that have no documents in the requested year. Modest value on top of annotations.

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 short sentences with zero filler, and the conditional requirement is placed after the core statement. The first sentence is a noun fragment without an explicit verb ('Lists…'), which is a minor structural weakness but costs no comprehension.

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 list tool with 100% schema coverage, annotations, and no output schema, the definition covers the key call conditions, including the one non-obvious required parameter. Missing pagination/result-size behavior is the main gap, but 'direct links' does signal what the agent will get back.

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 description coverage is 100%, so the baseline is 3, but the description adds a real constraint the schema does not express: the schema marks only 'coleccion' as required and gives 'anio' a null default, whereas the description discloses that anio is effectively mandatory for informes_auditoria. That is meaningful semantics beyond the structured fields, lifting it above baseline.

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?

Identifies the resource precisely — documents (archivos) belonging to an IESS collection — and hints at the return form with 'direct links'. It does not, however, distinguish itself from the many parallel archive-listing siblings (get_inec_publicacion_archivos, get_bce_pagina_archivos, get_sgr_sitrep_archivos), so an agent must rely on the 'IESS' qualifier alone to pick it. Clear verb+resource, no sibling differentiation.

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 line 'anio is required for informes_auditoria' is a genuine conditional usage rule that steers the agent for one enum value. Beyond that there is no statement of when to prefer this tool over the other archive/report tools, nor what to do when the requested collection is unknown. Implied usage only.

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