Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Buscar en todas las fuentes de Ecuador

search_ecuador
Read-only

Search Ecuador's open government data in one step: CKAN datasets, gob.ec trámites and regulations, SERCOP contracts, and SGR risk events; refine with source-specific tools.

Instructions

Unified first-step search across CKAN datasets, organizations, gob.ec trámites and regulations, SERCOP contracts and SGR risk events, a few hits per source. Drill down with the source-specific get_* tools; for CKAN datasets alone use search_datasets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results per section (default 5, max 10)
queryYesSearch terms in Spanish (e.g. "salud", "RUC", "medicinas")
formatNotext summary (default) or json structured result.text

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. Changed3 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 per section (default 5, max 10)"
    • addedInput schema / properties / query / description
      Added value: +"Search terms in Spanish (e.g. \"salud\", \"RUC\", \"medicinas\")"
  3. Changed5 schema fields changedv0.8.14
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"search_ecuadorArguments"
    • removedOutput schema / title
      Removed value: -"search_ecuadorDictOutput"
  4. First observedv0.8.12

TDQS

A4.5/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, destructiveHint=false, openWorldHint=true), lowering the bar. The description adds meaningful behavioral context not in annotations: it returns only 'a few hits per source' rather than exhaustive results, which sets correct expectations about output volume. It does not describe ordering or pagination, so it falls just short of a 5.

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 sentences, no filler. The source inventory and the two routing alternatives (get_* drill-down, search_datasets) are front-loaded, making the definition scannable and action-oriented.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, first-step discovery search with no output schema and annotations already covering safety, this description is sufficient: it identifies sources, result granularity, and the correct follow-up tools. Nothing an agent needs to invoke it correctly is missing.

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 query (Spanish terms), limit (default 5, max 10), and format (text/json). Baseline 3 is correct; the description's 'a few hits per source' loosely matches the limit semantics but adds no new parameter-level detail.

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 and a clearly bounded scope: a unified first-step search across named source families (CKAN datasets, organizations, gob.ec trámites/regulations, SERCOP contracts, SGR risk events). It explicitly distinguishes itself from search_datasets and the source-specific get_* tools, so an agent can route without opening another 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 ordering guidance: use this as the first step, drill down with the source-specific get_* tools, and use search_datasets when only CKAN datasets are needed. This is a rare, complete when/when-not/alternative statement.

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