Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Ver una tabla del boletín IEM del BCE

get_bce_iem_table
Read-only

Fetch a specific IEM table from Ecuador's BCE data by table_id, with optional date filtering and past bulletin selection. Returns a preview or filtered series.

Instructions

One IEM XLSX table (table_id from search_bce_iem): date-filterable series for the standard layout, a faithful preview otherwise. boletin_numero selects a past bulletin.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rowsNoMax rows returned (1-100, default 20).
desdeNoEarliest period to include, as YYYY, YYYY-MM or a month-year label.
hastaNoLatest period to include, same formats as desde.
formatNotext summary (default) or json structured result.text
table_idYesA table_id from search_bce_iem.
boletin_numeroNoPast bulletin number from search_bce_iem(historico=true); 0 means the latest.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.10.0
    • addedInput schema / properties / boletin_numero / description
      Added value: +"Past bulletin number from search_bce_iem(historico=true); 0 means the latest."
    • addedInput schema / properties / desde / description
      Added value: +"Earliest period to include, as YYYY, YYYY-MM or a month-year label."
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / hasta / description
      Added value: +"Latest period to include, same formats as desde."
    • addedInput schema / properties / rows / description
      Added value: +"Max rows returned (1-100, default 20)."
    • addedInput schema / properties / table_id / description
      Added value: +"A table_id from search_bce_iem."
  2. Changed8 schema fields changedv0.8.14
    • removedInput schema / properties / boletin_numero / title
      Removed value: -"Boletin Numero"
    • removedInput schema / properties / desde / title
      Removed value: -"Desde"
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / hasta / title
      Removed value: -"Hasta"
    • removedInput schema / properties / rows / title
      Removed value: -"Rows"
    • removedInput schema / properties / table_id / title
      Removed value: -"Table Id"
    • removedInput schema / title
      Removed value: -"get_bce_iem_tableArguments"
    • removedOutput schema / title
      Removed value: -"get_bce_iem_tableDictOutput"
  3. First observedv0.8.12

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, non-destructive), so the description earns credit for adding real context: that the standard layout yields date-filterable series while other layouts return a faithful preview, and that boletin_numero switches to a past bulletin. That is meaningful behavior beyond the annotations, though it stops short of noting size/pagination limits.

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 tightly packed sentences with no filler and the key identifier (table_id source) front-loaded. The 'faithful preview otherwise' clause is deliberately compressed and slightly cryptic, but nothing is wasted.

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 an output schema present, return values needn't be described, and the description covers the layout-dependent behavior plus bulletin selection. For a read-only table fetcher it is nearly complete, missing only guidance on row limits or large-table behavior.

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%, so the schema already documents all six parameters including formats and defaults. The description only reinforces the provenance of table_id and the role of boletin_numero, adding little beyond what the schema states. Baseline 3 is appropriate.

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 ('One IEM XLSX table') and ties it to the sibling search_bce_iem as the source of table_id, which distinguishes it from that search tool. The 'standard layout / faithful preview' split further clarifies what actually comes back. Slightly terse but an agent can tell what this fetches.

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?

It implies the workflow by naming search_bce_iem as the origin of table_id and search_bce_iem(historico=true) as the origin of boletin_numero, but never states explicitly when to call this instead of the search tool or what condition selects it. Usage is inferable rather than declared.

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