Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Listar secciones de un archivo institucional

list_archivo_secciones
Read-only

List the document archive sections for a selected Ecuadorian institution, such as ARCSA or Superbancos, to identify sections for retrieval.

Instructions

List the sections of one institution's document archive (ARCSA, Superbancos, SEPS, INEVAL, SGR, Educación Superior, SIPA, Petroecuador, Energy Ministry, CNE, BVG, BVQ). Next: get_archivo_seccion(fuente, seccion).

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.

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. Changed2 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."
  4. Addedv0.8.14

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds the enumeration of valid sources and the downstream call, but says nothing about result ordering, size, or whether sections are stable identifiers.

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: the purpose first, the next-step routing second. No padding, and the actionable 'Next:' directive is front-loaded in the second 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 simple read-only two-parameter list tool with full schema coverage and annotations, the description covers purpose, valid inputs, and the follow-up call. What's missing is result-shape detail (count/format specifics), but that is minor for such a simple 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 coverage is 100% and both parameters (fuente enum, format enum) are fully described in the schema. The description's source list mirrors the fuente enum and adds no new syntax or semantics beyond the schema.

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 (list) and resource (sections of one institution's document archive), and enumerates the valid instituciones (ARCSA, Superbancos, etc.). Clearly distinguishable from the sibling get_archivo_seccion, which fetches a single section.

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 names the natural next step: get_archivo_seccion(fuente, seccion). This defines the two-step workflow, though it doesn't name when to skip this and call get_archivo_seccion directly if you already know the section.

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