Skip to main content
Glama
DweskZ

EcuDataMCP

by DweskZ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Listar los recursos de un dataset

list_dataset_resources
Read-only

List files in a CKAN dataset with format, size, URL and dates, flagging periodic name series. Use with preview or query tools to inspect Ecuador open data.

Instructions

Files (resources) in a CKAN dataset with format, size, URL and dates, flagging name groups that look like periodic series. Next: preview_resource_data or query_resource_data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNotext summary (default) or json structured result.text
sourceNoCKAN portal; nacional (default), cuenca, latacunga or iadb.nacional
dataset_idYesThe dataset ID or slug

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 / dataset_id / description
      Added value: +"The dataset ID or slug"
    • addedInput schema / properties / format / description
      Added value: +"text summary (default) or json structured result."
    • addedInput schema / properties / source / description
      Added value: +"CKAN portal; nacional (default), cuenca, latacunga or iadb."
  3. Changed5 schema fields changedv0.8.14
    • removedInput schema / properties / dataset_id / title
      Removed value: -"Dataset Id"
    • removedInput schema / properties / format / title
      Removed value: -"Format"
    • removedInput schema / properties / source / title
      Removed value: -"Source"
    • removedInput schema / title
      Removed value: -"list_dataset_resourcesArguments"
    • removedOutput schema / title
      Removed value: -"list_dataset_resourcesDictOutput"
  4. First observedv0.8.12

TDQS

A4.2/5.0
Behavior4/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 safety profile is covered. The description adds genuinely useful behavior beyond that: the shape of the returned listing (format, size, URL, dates) and the fact that periodic-series name groups are flagged, which an agent could not infer from schema or annotations. Pagination/limits for large datasets remain unstated.

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 short sentences with zero filler: the listing scope is front-loaded and the follow-up routing is compressed into a single clause. Every phrase carries information.

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 the description compensates by naming the returned fields and the series-flagging behavior. Minor gaps remain: what a 'periodic series' flag actually looks like in the text vs json output, and whether results are capped or paginated for datasets with many resources.

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%, with both enums (format, source) and dataset_id fully documented in the schema, so the baseline is 3. The description adds nothing about the 'source' portal switch or the text-vs-json output choice, so it does not exceed the baseline.

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 ('Files (resources) in a CKAN dataset') and even enumerates the fields returned (format, size, URL, dates) plus a distinctive derived behavior (flagging name groups that look like periodic series). An agent can distinguish this from get_dataset_info (metadata) and get_resource_info (single resource) 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 Guidelines4/5

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

The trailing 'Next: preview_resource_data or query_resource_data' explicitly routes the agent to the follow-up tool once a resource is identified, which is real selection guidance. It stops short of stating when NOT to use this tool (e.g., use get_dataset_info for dataset-level metadata, or detect_series_pattern for the series analysis itself), so no exclusions are given.

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