Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Buscar indicadores en CEPALSTAT

search_cepalstat_indicadores
Read-only

Search CEPALSTAT's 2,059 regional indicators by name or thematic area to find demographic, economic, environmental, and SDG data. Use it to locate an indicator before retrieving Ecuador's values.

Instructions

Search CEPALSTAT's 2,059 regional indicators (demographic, economic, environmental, SDG). Next: get_cepalstat_indicador for Ecuador's values.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNo"es" (default) or "en"es
queryNoFree text matched (accent-insensitive) against the indicator's name or its thematic-area breadcrumb, e.g. "poblacion", "pobreza", "comercio exterior".
formatNotext summary (default) or json structured result.text

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. Changed3 schema fields changedv0.10.0
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / lang / description
      Added value: +"\"es\" (default) or \"en\""
    • addedInput schema / properties / query / description
      Added value: +"Free text matched (accent-insensitive) against the indicator's name or its thematic-area breadcrumb, e.g. \"poblacion\", \"pobreza\", \"comercio exterior\"."
  3. Changed5 schema fields changedv0.8.14
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / lang / title
      Removed value: -"Lang"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"search_cepalstat_indicadoresArguments"
    • removedOutput schema / title
      Removed value: -"search_cepalstat_indicadoresDictOutput"
  4. First observedv0.8.12

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds the corpus size (2,059 indicators) and the workflow handoff, but says nothing about result limits, pagination, or how an empty query behaves despite query defaulting to ''.

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, zero filler, with the resource and corpus size front-loaded before the routing hint. Nothing could be cut without losing information.

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

Completeness5/5

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

For a read-only, three-optional-parameter search tool with a fully documented schema and no output schema to explain, the definition covers the essentials: what is searched, how broad the corpus is, and which tool to call next with the results.

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 each parameter (lang, query, format) carries its own description including an example and accent-insensitivity note. The description adds no parameter meaning beyond the schema, so the baseline of 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 (search) and resource (CEPALSTAT's 2,059 regional indicators) with the topical scope spelled out (demographic, economic, environmental, SDG). It also names the sibling get_cepalstat_indicador as the follow-up, so an agent can distinguish it from the value-fetching tool without opening either schema.

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 only guidance is the terse 'Next: get_cepalstat_indicador for Ecuador's values', which implies a search-then-fetch workflow but never states when to prefer this tool over the many other search_* statistics siblings (search_inec_estadisticas, search_indicadores_bce, query_sut_indicador). Usage is inferable rather than explicit.

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