Skip to main content
Glama
ondata

CKAN MCP Server

by ondata

List CKAN Dataset Resources

ckan_list_resources
Read-onlyIdempotent

List dataset resources with format, size, DataStore status, and download URL. Assess file availability to determine data access method.

Instructions

List all resources in a dataset with a compact summary.

Returns a focused table of resources showing format, size, DataStore availability, and download URL. Use this to quickly assess what files a dataset contains before deciding how to access the data.

Args:

  • server_url (string): Base URL of CKAN server

  • id (string): Dataset ID or name

  • format_filter (string): Filter resources by format, case-insensitive (e.g., "CSV", "json", "XLSX")

  • response_format ('markdown' | 'json'): Output format

Returns: Compact resource summary with name, ID, format, size, DataStore flag, and URL

Examples:

Typical workflow: ckan_package_search → ckan_list_resources (assess available files) → ckan_datastore_search (for resources with DataStore=true)

When a resource has DataStore=false but its download URL belongs to a different (source) portal, the tool automatically probes the source portal for DataStore availability and reports source_datastore_active and source_portal_url so you can query the data there instead. Set check_source_portal=false to skip these extra HTTP calls.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesDataset ID or name
server_urlYesBase URL of the CKAN server
format_filterNoFilter resources by format, case-insensitive (e.g., 'CSV', 'json', 'XLSX')
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown
check_source_portalNoWhen true (default), probes the source portal for DataStore availability when a resource URL points to a different CKAN instance
Behavior5/5

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

Discloses extra behavior beyond annotations: returns a compact table, auto-probes source portal for DataStore availability when resource has DataStore=false, and adds source_datastore_active and source_portal_url fields. Also mentions the check_source_portal parameter to skip extra HTTP calls.

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?

Well-structured: starts with purpose, then return format, typical workflow, special behavior. Slightly verbose but every sentence adds value, and examples are included.

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

Completeness5/5

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

No output schema, but description explains what is returned (resource name, ID, format, size, DataStore flag, URL). Covers important details like source portal probing. Comprehensive given the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds meaning: explains typical use of format_filter, the effect of check_source_portal, and includes examples. Provides more context than the schema alone.

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?

Clearly states the tool lists all resources in a dataset with a compact summary, and explains the use case of quickly assessing files before deciding access. Distinguishes itself from sibling tools like ckan_datastore_search and ckan_package_show.

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?

Provides a typical workflow (ckan_package_search → ckan_list_resources → ckan_datastore_search) and explains when to use the tool. Does not explicitly state when not to use, but the workflow gives clear context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ondata/ckan-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server