Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Ver observaciones de un indicador CEPALSTAT

get_cepalstat_indicador
Read-only

Fetch observations for a CEPALSTAT indicator by country, with dimension IDs decoded to labels. Use an indicator_id from search_cepalstat_indicadores.

Instructions

Observations of one CEPALSTAT indicator for one country (Ecuador by default), with dimension ids decoded to labels. Take indicator_id from search_cepalstat_indicadores.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNo"es" (default) or "en"es
paisNoCountry to filter to (accent-insensitive, e.g. "Ecuador", "Peru").Ecuador
formatNotext summary (default) or json structured result.text
indicator_idYesAn "indicator_id" from search_cepalstat_indicadores.

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 / indicator_id / description
      Added value: +"An \"indicator_id\" from search_cepalstat_indicadores."
    • addedInput schema / properties / lang / description
      Added value: +"\"es\" (default) or \"en\""
    • addedInput schema / properties / pais / description
      Added value: +"Country to filter to (accent-insensitive, e.g. \"Ecuador\", \"Peru\")."
  3. Changed6 schema fields changedv0.8.14
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / indicator_id / title
      Removed value: -"Indicator Id"
    • removedInput schema / properties / lang / title
      Removed value: -"Lang"
    • removedInput schema / properties / pais / title
      Removed value: -"Pais"
    • removedInput schema / title
      Removed value: -"get_cepalstat_indicadorArguments"
    • removedOutput schema / title
      Removed value: -"get_cepalstat_indicadorDictOutput"
  4. First observedv0.8.12

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: dimension ids are decoded to labels, and country defaults to Ecuador, which shapes what the agent gets back. It omits any note on volume, pagination, or rate limits.

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?

Two sentences, no filler. The scoping constraints (one indicator, one country, default Ecuador, decoded labels) are front-loaded, and the dependency instruction follows immediately.

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?

No output schema exists, and the description partially compensates by describing the shape of the result (decoded dimension labels). With all four parameters documented and the indicator_id dependency stated, an agent has what it needs, though return format and result size remain unspecified.

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% and every parameter (lang, pais, format, indicator_id) already carries its own description, so the schema does the heavy lifting. The description only echoes the Ecuador default and the indicator_id source, adding no format or syntax detail beyond the schema.

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 resource and scope: observations of ONE CEPALSTAT indicator for ONE country, with dimension ids decoded to labels. This clearly separates it from the plural search_cepalstat_indicadores, though it does not explicitly distinguish itself from the other data-retrieval sibling get_serie_internacional.

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?

Explicitly names the prerequisite source for indicator_id ("Take indicator_id from search_cepalstat_indicadores"), which tells the agent it must search first. It gives no when-not guidance or mention of alternatives for the same data, so it stops just short of a full routing instruction.

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