Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Buscar temas estadísticos del INEC

search_inec_estadisticas
Read-only

Search INEC's statistical topic pages on ecuadorencifras.gob.ec by keyword to locate published aggregate series on prices, employment, poverty, and national accounts.

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

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 / 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\"."
  3. 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"
  4. First observedv0.8.12

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true, destructiveHint=false). The description adds domain context beyond that: the source domain, the approximate page count (~75), and the nature of the content (topic pages hosting aggregate series), which helps the agent understand what it will retrieve.

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 tightly written sentences, zero filler, with the resource and its scope front-loaded before the workflow pointer.

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 paginated search tool with full schema coverage and no output schema, the description is nearly complete: it says what is searched and what the results conceptually are. It stops short of explaining result shape, but annotations and schema carry most of the load.

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 the schema already documents limit, query, format, and offset with examples. The description adds no parameter syntax or semantics beyond that, so baseline 3 applies.

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 — INEC's ~75 statistical topic pages on ecuadorencifras.gob.ec — with concrete topical examples (IPC, ENEMDU, pobreza) and clarifies these are where aggregate series live. It distinguishes the workflow from get_inec_estadistica_files by naming it as the next step, though it doesn't contrast with search_inec_publicaciones or search_biinec_extras.

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?

"Next: get_inec_estadistica_files" conveys the intended workflow (find a topic, then fetch its files), which implies when to use this vs that tool. However, it gives no explicit when-to-use or when-not-to-use guidance versus the other INEC search siblings, leaving the agent to infer.

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