Opendata Canada

Search

search

Read-onlyIdempotent

Full-text search the open.canada.ca CKAN catalogue by keyword query, with optional CKAN filter query (fq), pagination (rows/start); returns dataset titles, descriptions, organizations, formats, and resource URLs.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`fq`	No
`rows`	No
`query`	Yes
`start`	No

Output Schema

TableJSON Schema

Name	Required	Description
`count`	No	Total number of packages matching query
`results`	No	Array of package objects
`search_facets`	No	Faceted search results

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 27, 2026

addedInput schema / examples

Added value: +[
+  {
+    "query": "climate data"
+  },
+  {
+    "query": "health statistics",
+    "rows": 10,
+    "start": 0
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "CKAN package search result",
+  "properties": {
+    "count": {
+      "description": "Total number of packages matching query",
+      "type": "integer"
+    },
+    "results": {
+      "description": "Array of package objects",
+      "items": {
+        "properties": {
+          "author": {
+            "description": "Package author",
+            "type": "string"
+          },
+          "author_email": {
+            "description": "Author email",
+            "type": "string"
+          },
+          "groups": {
+            "description": "Array of group/theme IDs",
+            "items": {
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "id": {
+            "description": "Package ID",
+            "type": "string"
+          },
+          "license_id": {
+            "description": "License ID",
+            "type": "string"
+          },
+          "maintainer": {
+            "description": "Package maintainer",
+            "type": "string"
+          },
+          "maintainer_email": {
+            "description": "Maintainer email",
+            "type": "string"
+          },
+          "metadata_created": {
+            "description": "Creation timestamp",
+            "type": "string"
+          },
+          "metadata_modified": {
+            "description": "Modification timestamp",
+            "type": "string"
+          },
+          "name": {
+            "description": "Package name/slug",
+            "type": "string"
+          },
+          "notes": {
+            "description": "Package description",
+            "type": "string"
+          },
+          "organization": {
+            "description": "Organization object",
+            "type": "object"
+          },
+          "owner_org": {
+            "description": "Owner organization ID",
+            "type": "string"
+          },
+          "private": {
+            "description": "Whether package is private",
+            "type": "boolean"
+          },
+          "resources": {
+            "description": "Array of resources",
+            "items": {
+              "properties": {
+                "description": {
+                  "type": "string"
+                },
+                "format": {
+                  "type": "string"
+                },
+                "id": {
+                  "type": "string"
+                },
+                "last_modified": {
+                  "type": "string"
+                },
+                "name": {
+                  "type": "string"
+                },
+                "url": {
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "tags": {
+            "description": "Array of tags",
+            "items": {
+              "properties": {
+                "id": {
+                  "type": "string"
+                },
+                "name": {
+                  "type": "string"
+                },
+                "vocabulary_id": {
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "title": {
+            "description": "Package title",
+            "type": "string"
+          },
+          "url": {
+            "description": "Package URL",
+            "type": "string"
+          },
+          "version": {
+            "description": "Package version",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "search_facets": {
+      "description": "Faceted search results",
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedMay 18, 2026

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 and destructiveHint=false, so the tool is known to be safe. The description adds behavioral context by specifying the exact catalogue, the nature of the search (full-text), and what data is returned (dataset titles, descriptions, etc.), which is beyond the annotations.

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?

A single sentence that is well-structured, front-loaded with the core purpose, and includes all essential details without extra words. Every part is informative.

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 the tool's complexity (4 parameters, output schema exists), the description covers purpose, all parameters, and return fields. Output schema presence means return value documentation is not required in the description. The description is fully sufficient.

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?

With schema description coverage at 0%, the description fully explains all four parameters: 'keyword query' for 'query', 'optional CKAN filter query (fq)', and 'pagination (rows/start)'. This provides complete semantic meaning beyond the bare 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 the tool performs full-text search on a specific catalogue (open.canada.ca CKAN), lists supported parameters (keyword query, filter query, pagination), and specifies return fields (titles, descriptions, organizations, formats, resource URLs). This differentiates it from siblings like 'search_within'.

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

Usage Guidelines2/5

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

The description does not provide guidance on when to use this tool versus alternatives such as 'search_within' or 'deep_research'. It describes functionality but omits contextual cues or exclusion criteria.

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

All Opendata Canada tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.