Skip to main content
Glama
Sign In
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Listar el catálogo de una fuente (ARCONEL, BCE, Contraloría, IESS, SUT, Judicatura)

list_catalogo
Read-only

List the catalog for a specified Ecuador open data source, so you can choose the right identifier before calling its get tool.

Instructions

List one source's catalog, the step before its get tool: arconel (get_arconel_reporte), bce_diarios (get_bce_indicador_diario), contraloria (get_contraloria_informe), iess (get_iess_archivos), sut and judicatura (get_sut_indicador_schema, query_sut_indicador with the same fuente).

Input Schema

NameRequiredDescriptionDefault
formatNotext summary (default) or json structured result.text
fuenteYesCatalog to list; see the list above.

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
    • changedInput schema / properties / fuente / enum
      Previous value: -[
-  "arconel",
-  "bce_diarios",
-  "contraloria",
-  "iess",
-  "sut"
-]New value: +[
+  "arconel",
+  "bce_diarios",
+  "contraloria",
+  "iess",
+  "sut",
+  "judicatura"
+]
  3. Addedv0.11.0

TDQS

A4.3/5.0
Behavior3/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 the safety profile is fully covered. The description adds the workflow-ordering relationship, which is useful context, but says nothing about return contents, pagination, or rate limits beyond what the format parameter implies.

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?

A single front-loaded sentence leads with the core action, then spends the rest on the source-to-tool mapping. Dense and list-heavy but every clause carries routing information; no filler.

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 read-only, two-parameter list tool with full schema coverage, annotations covering safety, and no output schema, the description supplies the one thing structured fields cannot: how this catalog relates to the get tools it precedes. Nothing critical is missing, though return-shape details are absent.

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 coverage is 100%, so the baseline is 3, but the description goes further by tying each fuente enum value to its specific downstream tool, which gives an agent a clearer mental model of what each catalog contains than the schema's generic 'Catalog to list; see the list above.'

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 one source's catalog') and immediately distinguishes itself from siblings by mapping each fuente value to the exact downstream get tool it precedes (get_arconel_reporte, get_bce_indicador_diario, etc.). An agent can identify the tool's role without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly frames the tool as 'the step before its get tool' and enumerates which get tool each source feeds into, leaving no inference about when to call this versus the downstream tools. This is a routing guide as much as a description.

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