Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Buscar organizaciones publicadoras

search_organizations
Read-only

Find institutions publishing open data on Ecuador’s CKAN portals, returning organization slugs for further info. Use search_datasets to discover datasets by topic.

Instructions

Search the institutions publishing on a CKAN portal (98+ on the national one: INEC, SRI, MSP, BCE...). Returns the slugs get_organization_info takes; to find datasets by topic use search_datasets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (1-based, default: 1)
queryNoOptional search term (e.g. "salud", "SRI", "INEC")
formatNotext summary (default) or json structured result.text
sourceNoCKAN portal; nacional (default), cuenca, latacunga or iadb.nacional
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. Changed5 schema fields changedv0.10.0
    • 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: +"Optional search term (e.g. \"salud\", \"SRI\", \"INEC\")"
    • addedInput schema / properties / source / description
      Added value: +"CKAN portal; nacional (default), cuenca, latacunga or iadb."
  3. Changed7 schema fields changedv0.8.14
    • 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 / source / title
      Removed value: -"Source"
    • removedInput schema / title
      Removed value: -"search_organizationsArguments"
    • removedOutput schema / title
      Removed value: -"search_organizationsDictOutput"
  4. First observedv0.8.12

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only, open-world, and non-destructive safety. The description adds valuable behavioral context by stating the return type ('slugs get_organization_info takes') and scope (98+ institutions), though it omits pagination and response-shape details.

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 with zero waste: the purpose and scope are front-loaded, the return-type integration follows, and the sibling routing closes the definition. Every sentence 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 tool with 100% schema coverage and annotations covering safety, the description is nearly complete: it states purpose, scale, return type, and alternative. It could say more about return structure or pagination behavior since no output schema exists, but it is sufficient for correct invocation.

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 all five parameters including defaults and enums. The description adds no parameter-level syntax or format details beyond what the schema provides, making the baseline 3 appropriate.

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 resource ('Search the institutions publishing on a CKAN portal'), gives scale and examples (98+ on national: INEC, SRI, MSP, BCE), and distinguishes from search_datasets. An agent can tell this apart from sibling tools without opening schemas.

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?

Explicitly names the alternative for a different goal ('to find datasets by topic use search_datasets') and explains the downstream use ('Returns the slugs get_organization_info takes'), giving clear when-to-use and alternative-condition 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