Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Buscar el calendario de publicaciones del BCE

search_bce_calendario
Read-only

Search Ecuador BCE's statistical release calendar for upcoming publication dates and reference periods, filtered by date, category, or periodicity; returns schedule info, not data values.

Instructions

BCE's forward-looking statistical release calendar: dates, category, periodicity and reference period. solo_proximas=true keeps upcoming releases. Says when data will be published, not the data itself; for values use get_indicador_bce.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
desdeNoRestrict to release date >= this date (YYYY-MM-DD).
hastaNoRestrict to release date <= this date (YYYY-MM-DD).
limitNoMax results (1-200, default 50).
queryNoFree text matched against the publication name or its observations note (accent-insensitive).
formatNotext summary (default) or json structured result.text
offsetNoPagination offset over the matched set.
categoriaNoExact category filter (accent-insensitive), e.g. "cuentas nacionales", "balanza de pagos y comercio exterior".
periodicidadNoExact periodicity filter, e.g. "Mensual", "Anual", "Trimestral", "Semanal".
solo_proximasNoIf true, only releases scheduled today or later.

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. Changed9 schema fields changedv0.10.0
    • addedInput schema / properties / categoria / description
      Added value: +"Exact category filter (accent-insensitive), e.g. \"cuentas nacionales\", \"balanza de pagos y comercio exterior\"."
    • addedInput schema / properties / desde / description
      Added value: +"Restrict to release date >= this date (YYYY-MM-DD)."
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / hasta / description
      Added value: +"Restrict to release date <= this date (YYYY-MM-DD)."
    • addedInput schema / properties / limit / description
      Added value: +"Max results (1-200, default 50)."
    • addedInput schema / properties / offset / description
      Added value: +"Pagination offset over the matched set."
    • addedInput schema / properties / periodicidad / description
      Added value: +"Exact periodicity filter, e.g. \"Mensual\", \"Anual\", \"Trimestral\", \"Semanal\"."
    • addedInput schema / properties / query / description
      Added value: +"Free text matched against the publication name or its observations note (accent-insensitive)."
    • addedInput schema / properties / solo_proximas / description
      Added value: +"If true, only releases scheduled today or later."
  3. Changed11 schema fields changedv0.8.14
    • removedInput schema / properties / categoria / title
      Removed value: -"Categoria"
    • 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 / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / offset / title
      Removed value: -"Offset"
    • removedInput schema / properties / periodicidad / title
      Removed value: -"Periodicidad"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / properties / solo_proximas / title
      Removed value: -"Solo Proximas"
    • removedInput schema / title
      Removed value: -"search_bce_calendarioArguments"
    • removedOutput schema / title
      Removed value: -"search_bce_calendarioDictOutput"
  4. First observedv0.8.12

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so safety is covered. The description adds useful behavioral context about the nature of the result set (a schedule of future releases, not observations) and the solo_proximas filter's effect.

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 clauses, front-loaded with purpose and followed by the filter hint and the disambiguation pointer. No filler sentences.

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 9-parameter, no-required-args search tool with no output schema, the description adequately conveys what comes back (publication dates plus metadata) and how to disambiguate from the value-fetching sibling. Minor gap: it doesn't describe pagination behavior, though offset/limit are schema-documented.

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 nine parameters are already documented (date bounds, limit range, offset, categoria/periodicidad examples, format enum). The description only restates solo_proximas, adding no meaning beyond the schema; 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+resource ('BCE's forward-looking statistical release calendar') and enumerates the returned fields (dates, category, periodicity, reference period). It explicitly separates itself from the sibling get_indicador_bce, which returns values rather than publication dates.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit routing rule: this tool 'says when data will be published, not the data itself; for values use get_indicador_bce.' An agent can pick between the two without opening either schema.

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