Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Buscar el catálogo estadístico del BCE

search_indicadores_bce
Read-only

Search BCEData indicator groups (monetary, fiscal, external, real sector) and series names to find relevant data, then use get_indicador_bce for details.

Instructions

Search BCEData indicator groups (monetary, fiscal, external, real sector), matching series names too. Not CPI or poverty (INEC). First call after 24h can take 10-15 s. Next: get_indicador_bce.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 20, max 100)
queryNoFree text matched against the group's description, its section/subsection, and its individual series labels (accent-insensitive)
formatNotext summary (default) or json structured result.text
offsetNoPagination offset over the matched set

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. Changed4 schema fields changedv0.10.0
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / limit / description
      Added value: +"Max results (default 20, max 100)"
    • addedInput schema / properties / offset / description
      Added value: +"Pagination offset over the matched set"
    • addedInput schema / properties / query / description
      Added value: +"Free text matched against the group's description, its section/subsection, and its individual series labels (accent-insensitive)"
  3. Changed6 schema fields changedv0.8.14
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / offset / title
      Removed value: -"Offset"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"search_indicadores_bceArguments"
    • removedOutput schema / title
      Removed value: -"search_indicadores_bceDictOutput"
  4. First observedv0.8.12

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, but the description adds a genuinely useful behavioral caveat absent from structured data: cold-start latency of 10-15 s after 24h. This is exactly the kind of operational detail that prevents a timeout-driven retry storm.

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 compact sentences front-loading purpose, then the exclusion, then the latency plus next-step. No filler and no repetition of schema content.

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 four-parameter search with full schema coverage and a safety-covering annotation set, the description supplies the missing pieces an agent needs — domain scope, sibling exclusion, latency, and the follow-up call. Minor gaps (e.g., pagination strategy across offset/limit) are already handled by the schema, so this is nearly complete.

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% — limit, query, format, and offset are each documented in the schema, including the accent-insensitive matching rule. The description reinforces that series names are matched, but adds no syntax or default detail beyond the schema, so baseline 3 applies.

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 and resource ('Search BCEData indicator groups'), scopes the domain (monetary, fiscal, external, real sector) and the matching behavior (series names too). It also explicitly excludes a confusing sibling domain (CPI/poverty = INEC) and names the follow-up tool, so an agent can distinguish it from search_inec_estadisticas and others.

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?

Gives an explicit negative boundary ('Not CPI or poverty (INEC)') and a clear next step ('Next: get_indicador_bce'), which routes the agent through a two-call workflow. It stops short of naming when to prefer other BCE siblings (e.g., search_bce_iem, search_bce_paginas), so it is strong but not fully exhaustive.

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