Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Buscar temas estadísticos del INEC

search_inec_estadisticas
Read-only

Find INEC statistical topic pages by keyword to discover published aggregate series like IPC, ENEMDU, and poverty data for Ecuador.

Instructions

INEC's ~75 statistical topic pages on ecuadorencifras.gob.ec (IPC, ENEMDU, pobreza, cuentas nacionales...), where published aggregate series live. Next: get_inec_estadistica_files.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 30, max 100)
queryNoFree text matched against the topic name (accent-insensitive), e.g. "precios", "empleo", "pobreza".
formatNotext summary (default) or json structured result.text
offsetNoPagination offset over the matched set

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 30, 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 topic name (accent-insensitive), e.g. \"precios\", \"empleo\", \"pobreza\"."
  2. 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_inec_estadisticasArguments"
    • removedOutput schema / title
      Removed value: -"search_inec_estadisticasDictOutput"
  3. First observedv0.8.12

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, covering the safety profile. The description adds structural context (the ~75-page scope, the site domain, the aggregate-series nature) which is useful, but says nothing about result ordering, rate limits, or pagination behavior beyond what the schema supplies.

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 tight sentences with zero waste: the resource description is front-loaded, and the follow-up routing is appended compactly. Nothing is padded.

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?

An output schema exists, so return-value explanation is unnecessary, and the description covers the domain, scope, and examples needed to call the tool. The remaining gap is disambiguation from sibling search tools.

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 limit, query, format, and offset are already documented in the schema, including the accent-insensitive matching and defaults. The description adds no parameter-level detail, so the baseline of 3 is appropriate.

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 identifies the resource precisely: INEC's ~75 statistical topic pages on ecuadorencifras.gob.ec, with concrete examples (IPC, ENEMDU, pobreza, cuentas nacionales) and the note that aggregate series live there. The verb is carried by the name rather than the description, but an agent can distinguish this from siblings like search_inec_publicaciones. It stops short of explicitly stating 'search by topic name'.

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 trailing 'Next: get_inec_estadistica_files' gives a useful follow-up workflow hint. However, there is no guidance on when to pick this over adjacent tools such as search_inec_publicaciones, search_anda, or search_datasets, leaving selection to inference.

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