Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Buscar organizaciones publicadoras

search_organizations
Read-only

Find institutions publishing datasets on Ecuadorian CKAN portals; filter by search term, source portal, and page, returning text or JSON.

Instructions

Search the institutions publishing on a CKAN portal (98+ on the national one: INEC, SRI, MSP, BCE...).

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)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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."
  2. 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"
  3. First observedv0.8.12

TDQS

B3.2/5.0
Behavior3/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 the safety profile is covered. The description adds the useful context that the national portal has 98+ publishers, but says nothing about pagination, result shape, or auth requirements beyond what the schema already conveys.

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?

One tight sentence, front-loaded with the action and scope, with examples appended for concreteness. No filler, though the parenthetical examples slightly crowd a single-sentence definition.

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

Completeness3/5

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

An output schema and full parameter docs already exist, so much is supplied structurally. However, the description says 'a CKAN portal' while the schema exposes four distinct sources (nacional, cuenca, latacunga, iadb), leaving the multi-portal nature under-explained for a search tool with no required parameters.

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 every parameter (page, query, format, source, page_size) is already documented in the schema with defaults, enums and ranges. The description adds no parameter-level detail, 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?

States a specific verb+resource ('Search the institutions publishing on a CKAN portal') and grounds it with concrete examples (INEC, SRI, MSP, BCE). It does not differentiate from the sibling get_organization_info, which an agent could plausibly confuse with this lookup.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given, and no alternative sibling (e.g. get_organization_info for a single org) is named. The agent must infer usage from the name alone.

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