Skip to main content
Glama
ondata

CKAN MCP Server

by ondata

List CKAN Groups

ckan_group_list
Read-onlyIdempotent

List all groups on a CKAN server to find thematic collections of datasets. Returns group names or full objects with metadata, supporting pagination and sorting.

Instructions

List all groups on a CKAN server.

Groups are thematic collections of datasets.

Args:

  • server_url (string): Base URL of CKAN server

  • all_fields (boolean): Return full objects vs just names (default: false)

  • sort (string): Sort field (default: "name asc")

  • limit (number): Maximum results (default: 100). Use 0 to get only the count via faceting

  • offset (number): Pagination offset (default: 0)

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

Returns: List of groups with metadata. When limit=0, returns only the count of groups with datasets.

Typical workflow: ckan_group_list → ckan_group_show (inspect one) → ckan_package_search with fq="groups:name" (browse its datasets)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort field and direction (e.g., 'name asc', 'package_count desc')name asc
limitNoMax groups to return. Use 0 to get only the count via faceting
offsetNoPagination offset
all_fieldsNoReturn full group objects (true) or just name slugs (false)
server_urlYesBase URL of the CKAN server (e.g., https://dati.gov.it/opendata)
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown
Behavior5/5

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

Annotations already indicate readOnly/ idempotent/ non-destructive. The description adds behavior details: limit default 100, limit=0 returns only count, and output format options. No contradictions.

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?

Description is well-structured and concise: purpose, explanation, parameters, returns, workflow. Every sentence adds value, no fluff.

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?

Given full annotations and schema coverage, the description provides complete context: usage, parameters, return behavior, and typical workflow. No gaps.

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

Parameters4/5

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

Schema covers 100% of parameters with descriptions. The description repeats them clearly and adds context for limit=0 returning count. Slight extra value but not significantly beyond 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 clearly states 'List all groups on a CKAN server' with specific verb and resource. It distinguishes from siblings like ckan_group_search and ckan_group_show via a typical workflow.

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 description provides a typical workflow (ckan_group_list → ckan_group_show → ckan_package_search) that implies when to use this tool. It could explicitly mention when not to use, but the workflow is clear.

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