Skip to main content
Glama
ondata

CKAN MCP Server

by ondata
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Find CKAN Portals

ckan_find_portals
Read-onlyIdempotent

Discover CKAN open data portals by country, language, or topic from a registry of over 950 portals worldwide.

Instructions

Search the live datashades.info registry of ~950 CKAN portals worldwide.

Use this tool to discover which CKAN portals exist for a country, language, or topic before querying them with other CKAN tools.

IMPORTANT — country parameter: always pass country name in English. If the user writes in another language (e.g. "Italia", "España", "Brasil"), translate to English ("Italy", "Spain", "Brazil") before calling this tool.

Args:

  • country (string): Country name in English (e.g. "Italy", "Brazil", "France")

  • query (string): Keyword to match against portal title (e.g. "transport", "health")

  • min_datasets (number): Minimum number of datasets (e.g. 100)

  • language (string): Portal default locale code (e.g. "it", "en", "pt_BR", "fr")

  • has_datastore (boolean): If true, return only portals with DataStore enabled (supports SQL queries)

  • limit (number): Max results to return (default 10, max 50)

Returns: Ranked list of matching portals with URL, country, CKAN version, dataset count, and DataStore status.

Typical workflow: ckan_find_portals (discover portal URL) → ckan_status_show (verify) → ckan_package_search (search datasets)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 10, max 50)
queryNoKeyword matched against portal title (case-insensitive)
countryNoCountry name in English (e.g. 'Italy', 'Brazil'). Translate from any language before passing.
languageNoPortal default locale code (e.g. 'it', 'en', 'pt_BR')
min_datasetsNoMinimum number of datasets
has_datastoreNoIf true, return only portals with DataStore plugin (required for SQL queries)

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

Annotations indicate read-only, open-world, idempotent, non-destructive behavior. The description adds specific context: searches a live registry, returns ranked list with details, and includes an important note about country parameter translation. No contradiction.

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?

The description is well-organized with sections, clear parameter list, and a typical workflow. Every sentence adds value; no redundancy.

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?

Despite lacking an output schema, the description specifies the return format (ranked list with URL, country, CKAN version, dataset count, DataStore status) and suggests a typical usage workflow, making it complete for agent understanding.

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 coverage is 100%, but the description adds extra meaning: country translation requirement, has_datastore SQL support, limit defaults/max. However, some parameters (e.g., language) lack additional nuance 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 'Search the live datashades.info registry of ~950 CKAN portals worldwide' and provides a typical workflow that distinguishes it from dataset-level tools like ckan_package_search.

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?

It explains when to use the tool (before querying other CKAN tools) and provides a typical workflow, but does not explicitly mention when not to use it or compare to alternative portal discovery methods.

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