EcuDataMCP

Overview Schema Source Related Servers Discussions Admin

Buscar tablas del boletín IEM del BCE

search_bce_iem

Read-only

Search BCE monthly IEM bulletin tables by keyword, including past bulletins via historico. Find trade, debt, fiscal, oil, and GDP tables before retrieving them.

Instructions

Search the Excel tables of BCE's monthly IEM bulletin (trade by country, debt, fiscal, oil, GDP detail). historico=true searches past bulletins. Next: get_bce_iem_table.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Max tables returned (default 20).
`query`	No	Free text matched against table titles and sections (accent-insensitive).
`format`	No	text summary (default) or json structured result.	text
`offset`	No	Pagination offset over the matched set.
`historico`	No	Also search past monthly bulletins, not just the latest.
`desde_anio`	No	Earliest bulletin year to search (implies historico).
`hasta_anio`	No	Latest bulletin year to search (implies historico).
`hash_archivos`	No	Download each discovered XLSX and report its SHA-256 (operator audit; slow).
`guardar_catalogo`	No	Save the full assembled catalog under IEM_CATALOG_DIR.
`max_hash_archivos`	No	Cap on files hashed when hash_archivos is set.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.13.0Oct 17, 2026

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null

Changed10 schema fields changedv0.10.0Sep 28, 2026

addedInput schema / properties / desde_anio / description

Added value: +"Earliest bulletin year to search (implies historico)."

addedInput schema / properties / format / description

Added value: +"text summary (default) or json structured result."

addedInput schema / properties / guardar_catalogo / description

Added value: +"Save the full assembled catalog under IEM_CATALOG_DIR."

addedInput schema / properties / hash_archivos / description

Added value: +"Download each discovered XLSX and report its SHA-256 (operator audit; slow)."

addedInput schema / properties / hasta_anio / description

Added value: +"Latest bulletin year to search (implies historico)."

addedInput schema / properties / historico / description

Added value: +"Also search past monthly bulletins, not just the latest."

addedInput schema / properties / limit / description

Added value: +"Max tables returned (default 20)."

addedInput schema / properties / max_hash_archivos / description

Added value: +"Cap on files hashed when hash_archivos is set."

addedInput schema / properties / offset / description

Added value: +"Pagination offset over the matched set."

addedInput schema / properties / query / description

Added value: +"Free text matched against table titles and sections (accent-insensitive)."

Changed12 schema fields changedv0.8.14Sep 27, 2026
- removedInput schema / properties / desde_anio / title
```
Removed value: -"Desde Anio"
```
- removedInput schema / properties / format / title
```
Removed value: -"Format"
```
- removedInput schema / properties / guardar_catalogo / title
```
Removed value: -"Guardar Catalogo"
```
- removedInput schema / properties / hash_archivos / title
```
Removed value: -"Hash Archivos"
```
- removedInput schema / properties / hasta_anio / title
```
Removed value: -"Hasta Anio"
```
- removedInput schema / properties / historico / title
```
Removed value: -"Historico"
```
- removedInput schema / properties / limit / title
```
Removed value: -"Limit"
```
- removedInput schema / properties / max_hash_archivos / title
```
Removed value: -"Max Hash Archivos"
```
- removedInput schema / properties / offset / title
```
Removed value: -"Offset"
```
- removedInput schema / properties / query / title
```
Removed value: -"Query"
```
- removedInput schema / title
```
Removed value: -"search_bce_iemArguments"
```
- removedOutput schema / title
```
Removed value: -"search_bce_iemDictOutput"
```
First observedv0.8.12Sep 27, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, covering the safety profile. The description adds the historico=true behavior for past bulletins and the workflow handoff, but does not mention rate limits, auth needs, or the slow nature of hash_archivos (which is only in the schema).

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?

Three sentences with zero waste, front-loading the core purpose before the historico flag and the next-step handoff. Every sentence earns its place by adding scope or workflow guidance.

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?

Given 10 optional parameters, full schema coverage, and no output schema, the description covers the core purpose, key behavioral flag (historico), and the next tool. It omits what the search returns (e.g., table identifiers or metadata) and pagination/format behavior, but those gaps are minor and largely covered by the schema.

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 all 10 parameters are already documented in the input schema. The description's note that 'historico=true searches past bulletins' largely duplicates the schema's own description and adds no new syntax or meaning; the baseline 3 is appropriate.

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 ('Search') and resource ('Excel tables of BCE's monthly IEM bulletin') with scope categories (trade by country, debt, fiscal, oil, GDP detail). The explicit 'Next: get_bce_iem_table' distinguishes it from the retrieval sibling, so an agent can tell them apart without opening schemas.

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?

Provides clear usage context: use for searching IEM tables, with historico=true for past bulletins, and the next step is get_bce_iem_table. No explicit exclusions or alternatives (e.g., search_bce_paginas) are named, but the context is sufficient to infer when to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Buscar tablas del boletín IEM del BCE

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools