Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Ver una organización y sus datasets

get_organization_info
Read-only

Fetch a CKAN organization and its datasets by slug, optionally filtering by title, to explore one Ecuadorian open-data publisher without topic-wide searches.

Instructions

One CKAN organization and its datasets, the way to browse a large publisher (e.g. sri-servicio-de-rentas-internas). Take the slug from search_organizations; query filters dataset titles. To search by topic across publishers use search_datasets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoFree text matched (accent-insensitive) against each dataset's title.
formatNotext summary (default) or json structured result.text
sourceNoCKAN portal; nacional (default), cuenca, latacunga or iadb.nacional
organization_idYesThe organization slug (e.g. "sri-servicio-de-rentas-internas")

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. Changed4 schema fields changedv0.10.0
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / organization_id / description
      Added value: +"The organization slug (e.g. \"sri-servicio-de-rentas-internas\")"
    • addedInput schema / properties / query / description
      Added value: +"Free text matched (accent-insensitive) against each dataset's title."
    • addedInput schema / properties / source / description
      Added value: +"CKAN portal; nacional (default), cuenca, latacunga or iadb."
  3. Changed6 schema fields changedv0.8.14
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / organization_id / title
      Removed value: -"Organization Id"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / properties / source / title
      Removed value: -"Source"
    • removedInput schema / title
      Removed value: -"get_organization_infoArguments"
    • removedOutput schema / title
      Removed value: -"get_organization_infoDictOutput"
  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 declare readOnlyHint/openWorldHint/destructiveHint, so safety is covered. The description adds real behavior: it discloses that this is a browse-style bulk listing, that 'query' filters dataset titles rather than doing a topic search, and that output can be a text summary or structured json. It stops short of describing pagination or result-size limits, which keeps it out of the top band.

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 short sentences, front-loaded with what the tool returns before the routing instructions. Every clause carries information: scope, sourcing of the slug, the query's filtering target, and the sibling alternative.

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?

There is no output schema and no annotation for return shape, so the description must carry that burden; it does so adequately by naming the payload (organization plus its datasets) and the two output formats. It is slightly thin on what fields come back per dataset and whether results are truncated, but an agent has enough to call it correctly.

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% and every parameter already carries a description with defaults and enum values, so the baseline is 3. The description reinforces the slug format and the title-filtering behavior of 'query' but adds no syntax, format, or constraint detail beyond the schema.

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?

The description states a specific verb+resource ('One CKAN organization and its datasets') and frames it functionally ('the way to browse a large publisher'). It explicitly separates itself from the two adjacent siblings, search_organizations and search_datasets, so an agent can pick correctly without opening a 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?

It gives an explicit prerequisite/ordering rule ('Take the slug from search_organizations') and an explicit alternative with the condition that selects it ('To search by topic across publishers use search_datasets'). Usage is fully resolved, including how to obtain the required parameter.

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