Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Ver archivos de una sección de un archivo institucional

get_archivo_seccion
Read-only

List downloadable files (title, URL, format) for a source and section ID, returning direct links to download rather than file contents.

Instructions

List the downloadable files (title, URL, format) in one section from list_archivo_secciones. Returns links, not file contents; download large files directly (preview/download tools cap at 5 MB).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNotext summary (default) or json structured result.text
fuenteYesOne of arcsa, superbancos, seps, ineval, sgr, senescyt, sipa, petroecuador, energia, cne, bvg, bvq.
seccionYesA section `id` from list_archivo_secciones.

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.12.0
    • changedInput schema / properties / fuente / description
      Previous value: -"One of arcsa, superbancos, seps, ineval, sgr, senescyt, sipa."New value: +"One of arcsa, superbancos, seps, ineval, sgr, senescyt, sipa, petroecuador, energia, cne, bvg, bvq."
    • changedInput schema / properties / fuente / enum
      Previous value: -[
-  "arcsa",
-  "superbancos",
-  "seps",
-  "ineval",
-  "sgr",
-  "senescyt",
-  "sipa"
-]New value: +[
+  "arcsa",
+  "superbancos",
+  "seps",
+  "ineval",
+  "sgr",
+  "senescyt",
+  "sipa",
+  "petroecuador",
+  "energia",
+  "cne",
+  "bvg",
+  "bvq"
+]
  3. Changed3 schema fields changedv0.10.0
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / fuente / description
      Added value: +"One of arcsa, superbancos, seps, ineval, sgr, senescyt, sipa."
    • addedInput schema / properties / seccion / description
      Added value: +"A section `id` from list_archivo_secciones."
  4. Addedv0.8.14

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, openWorld). The description usefully adds return semantics — 'returns links, not file contents' — and a size constraint on the alternative preview/download path, which is behavioral context the annotations don't provide.

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 tight sentences with the scope and return semantics front-loaded and no wasted words. Every clause carries information.

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, the description compensates by naming the return fields (title, URL, format) and clarifying that links, not contents, are returned. Combined with annotations covering safety, it is largely complete for a three-parameter listing tool.

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 the schema already documents all three parameters including both enums. The description's mention of title/URL/format refers to outputs rather than inputs and adds little beyond the schema, so the baseline 3 applies.

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 — list the downloadable files (title, URL, format) in one section — and anchors the resource to the sibling tool list_archivo_secciones. An agent can distinguish this from list_archivo_secciones and the download/preview tools without opening a schema.

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 positions the tool as the listing step that takes a section id from list_archivo_secciones, and adds a routing rule for the download side ('download large files directly; preview/download tools cap at 5 MB'). It stops short of explicitly stating when not to use it, so it's clear context without full exclusion logic.

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