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 Ecuador central bank IEM table by ID, with date filtering and past bulletin selection, returning text or JSON.

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.

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. 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."
  3. 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"
  4. 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 (readOnlyHint, destructiveHint=false), so the bar is lower. The description adds real behavioral context beyond them: for the 'standard layout' you get date-filterable series, otherwise a 'faithful preview' (i.e. filters may not apply). This output-variance disclosure is genuinely useful, though the phrasing is somewhat cryptic.

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 tight sentences, front-loaded with what the tool returns and where the id comes from. Nothing is wasted, though 'a faithful preview otherwise' is compressed to the point of ambiguity.

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-param, no-output-schema tool, the description covers what is returned (an XLSX table / text-or-json per the format param), the id source, and the bulletin selector. Pagination (rows) and format handling are left to the schema, which is acceptable given 100% coverage.

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 each parameter is already documented. The description reinforces the provenance of table_id and boletin_numero and the date-filterability of desde/hasta, but adds no syntax or semantics beyond the schema. 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 its sibling by naming search_bce_iem as the source of table_id, so an agent can tell it apart from the search tool. It stops short of a fully explicit 'this fetches one table by id' framing, but the pairing is clear.

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 only implied: the agent must infer that it should call search_bce_iem first to obtain a table_id, and search_bce_iem(historico=true) for a boletin_numero. There is no explicit when-to-use/when-not statement, though the input provenance gives practical guidance.

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