Skip to main content
Glama
Sign In
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Series internacionales con datos de Ecuador (WDI, IRENA, XM, Comtrade, FMI, OMS, OIT, ACNUR)

get_serie_internacional
Read-only

Retrieve Ecuador's international data series from World Bank, IMF, WHO, UN Comtrade, IRENA, ILO, UNHCR, and power-flow sources; filter by indicator, period, partner, or flow.

Instructions

International series for Ecuador via fuente: wdi (World Bank), irena (electricity), xm (Colombia-Ecuador power flows), comtrade (UN bilateral trade), imf (IMF SDMX), who (health), ilo (ILOSTAT labour), unhcr (refugees/asylum). Without indicador/flow, wdi/who/imf/ilo list their catalog (set query).

Input Schema

NameRequiredDescriptionDefault
cmdNocomtrade only: TOTAL or an HS code of 2, 4 or 6 digits.TOTAL
paisNowdi/irena/who/imf/ilo/unhcr: ISO3 code (irena also accepts the English name).ECU
tipoNoirena only: generacion (GWh), capacidad (MW) or ambos.ambos
claveNoimf/ilo only: SDMX key, dot-separated (ECU.CPI._T.IX.M).
desdeNoStart: a year (AAAA) for wdi/irena/who/unhcr, a date (AAAA-MM-DD) for xm, a period (AAAA, AAAA-MM) for imf/ilo.
flujoNocomtrade only: X (exports), M (imports) or ambos.ambos
hastaNoEnd, same format as desde.
limitNocatalog/flow listings only: maximum rows (1-200).
queryNowdi/who/imf/ilo: catalog search text, used when indicador is empty.
socioNocomtrade: partner as ISO3 (USA, CHN, COL, PER, PAN, ESP, NLD, ITA...) or M49 number; empty = 0 (World).
formatNotext summary (default) or json structured result.text
fuenteYeswdi, irena, xm, comtrade, imf, who, ilo or unhcr.
periodoNocomtrade only: one period, AAAA (frecuencia A) or AAAAMM (frecuencia M).
sentidoNoxm only: exportaciones (Colombia to Ecuador) or importaciones (Ecuador to Colombia).exportaciones
ultimosNoimf/ilo only: last N observations per series.
conexionNoirena only: All, On-grid or Off-grid.All
indicadorNowdi/who: indicator code.
agregacionNoxm only: dia or mes.dia
frecuenciaNocomtrade only: A (annual) or M (monthly).A
tecnologiaNoirena only: technology label substring (solar, hydro, Total Renewable...).

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. Changed14 schema fields changedv0.12.0
    • addedInput schema / properties / clave
      Added value: +{
+  "default": "",
+  "description": "imf/ilo only: SDMX key, dot-separated (ECU.CPI._T.IX.M).",
+  "type": "string"
+}
    • addedInput schema / properties / cmd
      Added value: +{
+  "default": "TOTAL",
+  "description": "comtrade only: TOTAL or an HS code of 2, 4 or 6 digits.",
+  "type": "string"
+}
    • changedInput schema / properties / desde / description
      Previous value: -"Start: a year (AAAA) for wdi/irena, a date (AAAA-MM-DD) for xm."New value: +"Start: a year (AAAA) for wdi/irena/who/unhcr, a date (AAAA-MM-DD) for xm, a period (AAAA, AAAA-MM) for imf/ilo."
    • addedInput schema / properties / flujo
      Added value: +{
+  "default": "ambos",
+  "description": "comtrade only: X (exports), M (imports) or ambos.",
+  "type": "string"
+}
    • addedInput schema / properties / frecuencia
      Added value: +{
+  "default": "A",
+  "description": "comtrade only: A (annual) or M (monthly).",
+  "enum": [
+    "A",
+    "M"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / fuente / description
      Previous value: -"wdi, irena or xm."New value: +"wdi, irena, xm, comtrade, imf, who, ilo or unhcr."
    • changedInput schema / properties / fuente / enum
      Previous value: -[
-  "wdi",
-  "irena",
-  "xm"
-]New value: +[
+  "wdi",
+  "irena",
+  "xm",
+  "comtrade",
+  "imf",
+  "who",
+  "ilo",
+  "unhcr"
+]
    • changedInput schema / properties / indicador / description
      Previous value: -"wdi only: WDI code."New value: +"wdi/who: indicator code."
    • changedInput schema / properties / limit / description
      Previous value: -"wdi catalog search only: maximum indicators (1-200)."New value: +"catalog/flow listings only: maximum rows (1-200)."
    • changedInput schema / properties / pais / description
      Previous value: -"wdi/irena: ISO3 code (irena also accepts the English name)."New value: +"wdi/irena/who/imf/ilo/unhcr: ISO3 code (irena also accepts the English name)."
    • addedInput schema / properties / periodo
      Added value: +{
+  "default": "",
+  "description": "comtrade only: one period, AAAA (frecuencia A) or AAAAMM (frecuencia M).",
+  "type": "string"
+}
    • changedInput schema / properties / query / description
      Previous value: -"wdi only: catalog search text, used when indicador is empty."New value: +"wdi/who/imf/ilo: catalog search text, used when indicador is empty."
    • addedInput schema / properties / socio
      Added value: +{
+  "default": "",
+  "description": "comtrade: partner as ISO3 (USA, CHN, COL, PER, PAN, ESP, NLD, ITA...) or M49 number; empty = 0 (World).",
+  "type": "string"
+}
    • addedInput schema / properties / ultimos
      Added value: +{
+  "default": 0,
+  "description": "imf/ilo only: last N observations per series.",
+  "type": "integer"
+}
  3. Addedv0.11.0

TDQS

A3.7/5.0
Behavior4/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 safety is covered. The description adds real behavior beyond that: the dual mode where an empty indicador/flow triggers a catalog listing rather than a data fetch, plus per-source semantics (xm is cross-border power flows, comtrade is bilateral trade). It omits any note on auth, rate limits, or result size.

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 sentences, no filler, with the core purpose front-loaded before the source mapping. The second sentence is dense and slightly ambiguous ('Without indicador/flow'), which keeps it just under a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 20-parameter, no-output-schema dispatcher this is adequate but thin. It explains source selection and catalog discovery, yet says nothing about the shape of returned data (text summary vs json is only in the schema) or which parameter combinations are valid per source, which is the main risk area for a multi-source tool.

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 the baseline is 3, but the description earns extra by decoding the `fuente` enum values and explaining the indicador/query interaction that the schema alone leaves implicit. It does not clarify how the source-specific parameters (clave, sentido, tecnologia, etc.) combine when several are supplied.

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?

The description names a specific verb+resource (retrieve international series for Ecuador) and enumerates the eight `fuente` sources with a short gloss for each (wdi=World Bank, irena=electricity, xm=Colombia-Ecuador power flows, comtrade=UN bilateral trade, etc.). That is far more specific than the tool name alone. It does not, however, position itself against nearby siblings such as get_cepalstat_indicador or search_indicadores_bce, so it stays 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?

It gives one genuine workflow hint: with an empty indicador/flow, wdi/who/imf/ilo return their catalog, and `query` is the search text. That is useful implied usage. It never states when to pick this tool over the BCE or CEPALSTAT alternatives, and there are no exclusions or prerequisites, so guidance remains partial.

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