Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Buscar datasets en el portal de datos abiertos

search_datasets
Read-only

Search Ecuadorian open-data datasets across CKAN portals, filter by category or source, and sort by recent to find newly updated records.

Instructions

Search CKAN open-data datasets (national portal by default; see source). Use sort="recent" without a query to browse new or updated datasets. Next: list_dataset_resources. For trámites, regulations or contracts use search_ecuador.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (1-based, default: 1)
sortNo"relevance" (default, CKAN's own ranking) or "recent" (sort by metadata_modified descending, to discover newly added or freshly refreshed datasets)relevance
queryNoSearch keywords (e.g. "empleo", "salud", "presupuesto", "SRI recaudación").
fieldsNoComma-separated dataset keys to keep in the JSON output (e.g. "name,title,metadata_modified"); applied after compact.
formatNotext summary (default) or json structured result.text
sourceNoCKAN portal; nacional (default), cuenca, latacunga or iadb.nacional
compactNoShrink each dataset in the JSON output to id, name, title, metadata_modified, organization and its resources (id, name, format, size, url).
categoryNoOptional category filter (e.g. "sal" for Salud, "edu" for Educación).
page_sizeNoResults per page (default: 20, max: 100)

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. Changed2 schema fields changedv0.12.0
    • addedInput schema / properties / compact
      Added value: +{
+  "default": false,
+  "description": "Shrink each dataset in the JSON output to id, name, title, metadata_modified, organization and its resources (id, name, format, size, url).",
+  "type": "boolean"
+}
    • addedInput schema / properties / fields
      Added value: +{
+  "default": "",
+  "description": "Comma-separated dataset keys to keep in the JSON output (e.g. \"name,title,metadata_modified\"); applied after compact.",
+  "type": "string"
+}
  3. Changed7 schema fields changedv0.10.0
    • addedInput schema / properties / category / description
      Added value: +"Optional category filter (e.g. \"sal\" for Salud, \"edu\" for Educación)."
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / page / description
      Added value: +"Page number (1-based, default: 1)"
    • addedInput schema / properties / page_size / description
      Added value: +"Results per page (default: 20, max: 100)"
    • addedInput schema / properties / query / description
      Added value: +"Search keywords (e.g. \"empleo\", \"salud\", \"presupuesto\", \"SRI recaudación\")."
    • addedInput schema / properties / sort / description
      Added value: +"\"relevance\" (default, CKAN's own ranking) or \"recent\" (sort by metadata_modified descending, to discover newly added or freshly refreshed datasets)"
    • addedInput schema / properties / source / description
      Added value: +"CKAN portal; nacional (default), cuenca, latacunga or iadb."
  4. Changed9 schema fields changedv0.8.14
    • removedInput schema / properties / category / title
      Removed value: -"Category"
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / page / title
      Removed value: -"Page"
    • removedInput schema / properties / page_size / title
      Removed value: -"Page Size"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / properties / sort / title
      Removed value: -"Sort"
    • removedInput schema / properties / source / title
      Removed value: -"Source"
    • removedInput schema / title
      Removed value: -"search_datasetsArguments"
    • removedOutput schema / title
      Removed value: -"search_datasetsDictOutput"
  5. First observedv0.8.12

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds useful context (default portal, browse-without-query behavior) but says nothing about pagination limits beyond the schema, rate limits, or result shape, so it only modestly exceeds the annotations.

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?

Three tight sentences, front-loaded with purpose and followed by the two highest-value usage hints (browse mode and the sibling handoff). No filler.

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 9-parameter, zero-required search tool with no output schema, the description covers purpose, fallback source, browsing mode, follow-up tool and domain routing. It stops short of describing output format behavior (text vs json interplay with compact/fields), but the annotations and schema carry that load.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds real meaning on top: it explains the intent of sort="recent" (browse without a query) and clarifies portal defaulting via "see source", which is behavioral guidance the enum definitions alone do not convey.

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+resource ("Search CKAN open-data datasets") and immediately scopes the default source. It distinguishes itself from siblings by naming search_ecuador for trámites/regulations/contracts, so an agent can route without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use guidance: sort="recent" with no query to browse new/updated datasets, a named next step (list_dataset_resources), and a named alternative domain (search_ecuador). This is exactly the routing detail agents need.

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