Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Buscar publicaciones de Ecuador en Cifras

search_inec_publicaciones
Read-only

Search INEC publications on Ecuador en Cifras by keyword to find recent releases of statistical operations and avoid stale topic pages.

Instructions

Every INEC post on Ecuador en Cifras, newest first; use for the latest release of an operation (topic pages can go stale). Next: get_inec_publicacion_archivos.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 20, max 100).
queryNoFree text matched against title/content (e.g. "ENEMDU anual 2025", "inflación julio", "censo").
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 20, 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 title/content (e.g. \"ENEMDU anual 2025\", \"inflación julio\", \"censo\")."
  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_publicacionesArguments"
    • removedOutput schema / title
      Removed value: -"search_inec_publicacionesDictOutput"
  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 readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description adds genuine behavioral value by stating ordering ('newest first') and completeness ('Every INEC post'), plus the downstream tool to call.

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 compact clauses, zero filler, with the ordering constraint front-loaded ahead of the usage hint. Every phrase earns its place.

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 search/list tool with full schema coverage, no output schema, and read-only annotations, the description is nearly complete and points to the follow-up tool. It omits what a 'post' contains or pagination expectations, but those are minor.

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% (limit, query, format, offset all documented), so the schema carries parameter meaning. The description adds no syntax or filtering detail beyond it, making the baseline 3 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?

States a specific verb+resource: lists every INEC post on 'Ecuador en Cifras', ordered newest first. It distinguishes itself from stale topic pages, though it doesn't explicitly contrast with the close sibling search_inec_estadisticas. An agent can still tell what it returns.

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?

Gives clear context ('use for the latest release of an operation') and a routing hint ('Next: get_inec_publicacion_archivos'). It lacks explicit when-not-to-use or a named alternative among the many search_* siblings, so it stops short of full routing guidance.

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