Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Ver archivos de un tema estadístico del INEC

get_inec_estadistica_files
Read-only

Retrieve INEC topic page file links—bulletins, methodology, and historical series—from a search result URL, filtered by year and returned as text or JSON.

Instructions

File links (bulletins, methodology, historical series) on one INEC topic page from search_inec_estadisticas.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesA topic URL from search_inec_estadisticas's "url" field (must be on ecuadorencifras.gob.ec)
yearNoOptional reference year; keeps only that year's files (each file carries a "year" parsed from its name or folder)
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. Changed1 schema field changedv0.12.0
    • addedInput schema / properties / year
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional reference year; keeps only that year's files (each file carries a \"year\" parsed from its name or folder)"
+}
  3. Changed2 schema fields changedv0.10.0
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / url / description
      Added value: +"A topic URL from search_inec_estadisticas's \"url\" field (must be on ecuadorencifras.gob.ec)"
  4. Changed4 schema fields changedv0.8.14
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / url / title
      Removed value: -"Url"
    • removedInput schema / title
      Removed value: -"get_inec_estadistica_filesArguments"
    • removedOutput schema / title
      Removed value: -"get_inec_estadistica_filesDictOutput"
  5. First observedv0.8.12

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare read-only, non-destructive, open-world behavior, so the safety profile is clear. The description adds that the output consists of file links (bulletins, methodology, historical series), but does not cover rate limits, auth, or return structure.

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?

Single, front-loaded sentence with no filler. It delivers purpose, scope, and source in one clause.

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 three-parameter read-only tool with no output schema, the description covers what is returned and where the required URL comes from. It omits return format details and the optional year/format filters, but those are handled by the schema and annotations.

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 url, year, and format are fully documented in the schema. The description only implies the url source and does not add semantic detail beyond the schema; baseline 3 applies.

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 the resource ('File links') and scope ('one INEC topic page'), with examples of file types. It ties the tool to search_inec_estadisticas, distinguishing it from that search tool, but does not explicitly differentiate from the similar get_inec_publicacion_archivos sibling.

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?

Clearly directs the agent to use a topic URL from search_inec_estadisticas, establishing the intended workflow. It gives no exclusions or alternative tools, but the source dependency is explicit.

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