Skip to main content
Glama
Sign In
EcuDataMCP

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Buscar publicaciones de Ecuador en Cifras

search_inec_publicaciones
Read-only

Search INEC publications from Ecuador en Cifras in reverse-chronological order to identify an operation's current release by title or content when topic pages are stale.

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_inec_publicaciones"
  }
}

Input 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.

Output Schema

NameRequiredDescriptionDefault
totalNo
offsetNo
sourceNo
metadatosYes
url_fuenteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.15.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "metadatos": {
+      "properties": {
+        "contrato": {
+          "const": "ecudatamcp.response.v1"
+        }
+      },
+      "required": [
+        "contrato"
+      ],
+      "type": "object"
+    },
+    "offset": {},
+    "source": {},
+    "total": {},
+    "url_fuente": {}
+  },
+  "required": [
+    "metadatos"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changedv0.13.0
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null
  3. 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\")."
  4. 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"
  5. First observedv0.8.12

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered; the description adds real context on top: complete coverage of all posts, newest-first ordering, and a warning that topic pages can be stale. It omits nothing critical, though it says nothing about pagination depth or how large the corpus is beyond the schema's limit/offset.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact clauses with the scoping fact front-loaded and the follow-up step last; nothing is wasted. The telegraphic, fragment-heavy style is efficient but slightly clipped, which keeps it just short of ideal readability.

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?

With an output schema present, return values need no explanation, and all four parameters are documented in the schema. The description covers scope, ordering, use case and the natural next tool, leaving only marginal gaps such as how results relate to the archive-fetching sibling.

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 query, limit, offset and format are all documented with defaults and examples. The description adds no parameter-level meaning (e.g. what 'query' matches, or when to prefer format=json), so the 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?

The fragment "Every INEC post on Ecuador en Cifras, newest first" states the resource, the scope (all posts, unfiltered) and the ordering, so an agent knows it is a full enumeration of INEC publications. The verb is implied rather than stated (no "list"/"search"), and it does not name the sibling it is preferable to, only alluding to "topic pages".

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?

"use for the latest release of an operation (topic pages can go stale)" gives a concrete selection condition plus the reason, which is exactly the kind of routing signal an agent needs. It also chains forward with "Next: get_inec_publicacion_archivos", though it never names the alternative to pick when you want historical or topic-indexed results instead.

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