Skip to main content
Glama
Sign In
EcuDataMCP

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Ver archivos de una publicación del INEC

get_inec_publicacion_archivos
Read-only

Retrieve file links (PDF, XLSX, CSV, ZIP) for an INEC publication using its ID or URL from search results; for ZIP archives, list contents before reading a member.

Instructions

File links (PDF/XLSX/CSV/ZIP) in one INEC publication (id or URL from search_inec_publicaciones). For a ZIP, next: list_zip_contents, then read_zip_member.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "post": "<post>"
    },
    "name": "get_inec_publicacion_archivos"
  }
}

Input 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

Output Schema

NameRequiredDescriptionDefault
totalNo
sourceNo
archivosNo
metadatosYes
url_fuenteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.15.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "archivos": {},
+    "metadatos": {
+      "properties": {
+        "contrato": {
+          "const": "ecudatamcp.response.v1"
+        }
+      },
+      "required": [
+        "contrato"
+      ],
+      "type": "object"
+    },
+    "source": {},
+    "total": {},
+    "url_fuente": {}
+  },
+  "required": [
+    "metadatos"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changedv0.13.0
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null
  3. 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."
  4. 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"
  5. First observedv0.8.12

TDQS

A4.2/5.0
Behavior4/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 safety is covered and the description need not restate it. The description adds real behavioral value by disclosing the returned artifact types (PDF/XLSX/CSV/ZIP) and, critically, that a ZIP result is not itself readable and requires the two-step follow-up workflow.

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?

Two short sentences, zero filler. The resource and its input source come first, and the conditional ZIP workflow is appended exactly where it is needed.

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 an output schema present, return-shape explanation is not required, and the description covers purpose, input provenance and the downstream ZIP path. Minor gaps remain around what happens with non-ZIP results and whether all files are returned, but nothing essential for a correct call is missing.

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 coverage is 100%, so both parameters (post, format) are already fully documented with enum and default. The description only echoes the id/URL semantics already in the schema, adding provenance ('from search_inec_publicaciones') but no new format details, which matches the baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('File links ... in one INEC publication') plus the file types returned and the input provenance (id or URL from search_inec_publicaciones). An agent can immediately tell this is the per-publication file listing, distinct from the catalog search sibling it names.

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?

Explicitly routes the agent: take the id/URL from search_inec_publicaciones, and if the result is a ZIP, continue with list_zip_contents then read_zip_member. This is concrete chaining guidance; only a 'when not to use this' exclusion is absent, and no obvious competing tool exists for this step.

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