Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Buscar archivos publicados por una institución

search_archivos
Read-only

Search Ecuadorian public institution catalogs for file links by source and keyword, returning download URLs only—not file contents.

Instructions

File links from one institution's catalog, filtered by text: SRI, MEF, SENAE, Census 2022, MINEDEC, SENESCYT, MSP, CNIG, Trabajo, ARCOTEL and BCE (remesas, comex prices, latest publications). Links, not contents.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax files returned (1-100, default 50).
queryNoFree text matched (accent-insensitive) against each file's title and source-specific fields.
formatNotext summary (default) or json structured result.text
fuenteYesCatalog to search; see the list above.
offsetNoPagination offset over the matched files.
formatoNoOptional exact file format (PDF, XLSX, CSV, ZIP...); not for sri_datasets, sri_recaudacion or censo.

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.11.0
    • addedInput schema / properties / formato
      Added value: +{
+  "default": "",
+  "description": "Optional exact file format (PDF, XLSX, CSV, ZIP...); not for sri_datasets, sri_recaudacion or censo.",
+  "type": "string"
+}
    • changedInput schema / properties / fuente / enum
      Previous value: -[
-  "sri_datasets",
-  "sri_recaudacion",
-  "mef",
-  "senae",
-  "censo",
-  "minedec",
-  "senescyt",
-  "msp",
-  "cnig",
-  "trabajo_boletin",
-  "salarios",
-  "arcotel_boletines",
-  "arcotel_mensuales"
-]New value: +[
+  "sri_datasets",
+  "sri_recaudacion",
+  "mef",
+  "senae",
+  "censo",
+  "minedec",
+  "senescyt",
+  "msp",
+  "cnig",
+  "trabajo_boletin",
+  "salarios",
+  "arcotel_boletines",
+  "arcotel_mensuales",
+  "bce_remesas",
+  "bce_precios_comex",
+  "bce_publicaciones"
+]
  3. Addedv0.10.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, openWorld, non-destructive), and the description adds a genuinely useful behavioral fact beyond them: it returns links, not file contents. It also signals that recency varies by source ('latest publications'). It does not describe pagination behavior or result volumes.

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?

Two sentences, scope front-loaded ('File links from one institution's catalog, filtered by text') with the clarifying 'Links, not contents' tacked on at the end. The institution list is long but carries source-enumeration value; little waste overall.

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 6-parameter, read-only search tool with full schema coverage, an annotations safety profile and no output schema, the description covers purpose, search scope, sources and output type. Minor gaps in how text matching behaves and pagination limits remain.

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 six parameters and the enum values. The description adds only human-readable groupings of the fuente enum (SRI, MEF, SENAE, BCE sub-catalogs), which is a marginal semantic gain over structured data.

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 a specific verb+resource — retrieving file links from one institution's catalog, filtered by text — and enumerates the source institutions. The clause 'Links, not contents' distinguishes it from content-fetching siblings like read_pdf or download_resource, though it never names a sibling outright.

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

Usage Guidelines3/5

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

Usage is implied: query a single institution's catalog by text. There is no explicit statement of when to prefer this over search_datasets, list_archivo_secciones, or the many other search_* siblings, and no exclusions or prerequisites are given.

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