Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Ver una categoría temática

get_category_info
Read-only

Fetch details and sample datasets for a CKAN category slug from Ecuadorian open data portals, so users can inspect thematic data available for analysis.

Instructions

Details and sample datasets for one CKAN thematic category (name from list_categories).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNotext summary (default) or json structured result.text
sourceNoCKAN portal; nacional (default), cuenca, latacunga or iadb.nacional
categoryYesCategory slug/name from list_categories
include_datasetsNoInclude sample datasets in the category (default True)

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 / category / description
      Added value: +"Category slug/name from list_categories"
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / include_datasets / description
      Added value: +"Include sample datasets in the category (default True)"
    • 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 / category / title
      Removed value: -"Category"
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / include_datasets / title
      Removed value: -"Include Datasets"
    • removedInput schema / properties / source / title
      Removed value: -"Source"
    • removedInput schema / title
      Removed value: -"get_category_infoArguments"
    • removedOutput schema / title
      Removed value: -"get_category_infoDictOutput"
  4. First observedv0.8.12

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safe-read profile is covered. The description adds only the fact that sample datasets may be included; it says nothing about how many are returned, truncation, or portal-dependent behavior across the four sources.

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?

A single economical sentence with the resource and scope front-loaded and zero filler. It is slightly under-explained rather than over-long, but there is no wasted text.

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?

With no output schema, the description does signal what comes back ('details and sample datasets'), which is the key return-value hint for a read-only informational tool. It omits how the response varies by the format parameter and by source portal, which would round it out.

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 format, source, category and include_datasets are all documented in the schema, including enum values and defaults. The description's only parameter hint ('name from list_categories') duplicates the schema's own wording, adding no new meaning. Baseline 3 applies.

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 (retrieves details + sample datasets) for a specific resource (one CKAN thematic category) and scopes it to a single item, which cleanly distinguishes it from the sibling list_categories, which enumerates them.

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

Usage Guidelines3/5

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

The parenthetical '(name from list_categories)' implies the prerequisite that you must first call list_categories to obtain a valid category, but there is no explicit when-to-use guidance, no exclusions, and no routing away from alternatives such as search_datasets for broader dataset discovery.

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