Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Ver serie de un indicador BCEData

get_indicador_bce
Read-only

Retrieve time series data for an Ecuadorian BCE indicator group by its ID, with date range, frequency, and unit filters. Returns text summary or JSON.

Instructions

Time series of one BCEData group (id_grupo from search_indicadores_bce), with optional YYYY-MM range, frequency and unit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
desdeNoStart period as YYYY-MM.
hastaNoEnd period as YYYY-MM.
formatNotext summary (default) or json structured result.text
unidadNoVaries by group (e.g. "Millones de USD", "Indice", "Porcentaje").
id_grupoYesThe group id from search_indicadores_bce.
frecuenciaNoSemanal | Mensual | Trimestral | Anual.

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 / desde / description
      Added value: +"Start period as YYYY-MM."
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / frecuencia / description
      Added value: +"Semanal | Mensual | Trimestral | Anual."
    • addedInput schema / properties / hasta / description
      Added value: +"End period as YYYY-MM."
    • addedInput schema / properties / id_grupo / description
      Added value: +"The group id from search_indicadores_bce."
    • addedInput schema / properties / unidad / description
      Added value: +"Varies by group (e.g. \"Millones de USD\", \"Indice\", \"Porcentaje\")."
  3. Changed8 schema fields changedv0.8.14
    • removedInput schema / properties / desde / title
      Removed value: -"Desde"
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / frecuencia / title
      Removed value: -"Frecuencia"
    • removedInput schema / properties / hasta / title
      Removed value: -"Hasta"
    • removedInput schema / properties / id_grupo / title
      Removed value: -"Id Grupo"
    • removedInput schema / properties / unidad / title
      Removed value: -"Unidad"
    • removedInput schema / title
      Removed value: -"get_indicador_bceArguments"
    • removedOutput schema / title
      Removed value: -"get_indicador_bceDictOutput"
  4. First observedv0.8.12

TDQS

A3.7/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 covered structurally. The description adds no behavioral context beyond that, such as response format for the text default or any limits, so a baseline 3 is appropriate for a read-only query tool.

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?

A single sentence with zero waste; the resource and its disambiguating id source are front-loaded before the optional filters.

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, single-required-parameter query tool with full schema coverage and no output schema, the description supplies what an agent needs to call it. Only the absence of any hint about return shape or noting it as one of several BCE series tools keeps it from a 5.

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 description coverage is 100%, so all six parameters (including YYYY-MM ranges, frecuencia enum and unidad) are already documented. The description reinforces the optional range/frequency/unit framing and the id_grupo provenance, adding light value on top of the schema but nothing the schema lacks.

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 ('Time series of one BCEData group') and ties id_grupo back to its source tool, search_indicadores_bce, which helps separate it from the many other retrieval siblings. It does not explicitly name what it is not (e.g. get_bce_indicador_diario or get_bce_iem_table), so differentiation stops short of a 5.

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?

The description implies usage by noting id_grupo comes from search_indicadores_bce, which is genuine routing guidance for the required parameter. However it gives no explicit when-to-use vs when-not, and no mention of the adjacent daily/IEM tools that could otherwise be confused with it.

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