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

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

Output 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.

Changed7 schema fields changedOct 13, 2026
- changedOutput schema / properties / results / items / properties / author / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / results / items / properties / author_email / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / results / items / properties / maintainer / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / results / items / properties / resources / items / properties / description / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / results / items / properties / resources / items / properties / last_modified / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / results / items / properties / url / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
- changedOutput schema / properties / results / items / properties / version / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```

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

A3.6/5.0

Behavior3/5

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

Annotations already declare the full safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), so the description carries a lighter burden. It adds the return shape (titles, descriptions, organizations, formats, resource URLs) and the CKAN catalogue scope, but since an output schema exists that return detail is partly redundant and no rate-limit, auth, or pagination-limit behavior is disclosed.

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?

A single front-loaded sentence with the resource named first and optional parameters grouped in a subordinate clause. Dense but every clause maps to a parameter or the return shape, with no filler.

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?

With an output schema covering return values and annotations covering the safety profile, the description's job is mainly purpose, scope, and parameters — all of which are present. The main residual gap is the absence of guidance on fq syntax and pagination defaults, which is minor given the examples in the schema.

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 description coverage is 0%, so the description must compensate and largely does: it identifies 'query' as the keyword, 'fq' as a CKAN filter query, and 'rows'/'start' as pagination. It does not explain fq syntax or default/max values for rows, leaving some gap, but it meaningfully documents all four parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ('full-text search') and a tightly scoped resource ('the open.canada.ca CKAN catalogue'), which implicitly separates it from generic siblings like package, groups, and organizations. It stops short of naming search_within or any other alternative, so sibling differentiation is left to inference rather than stated.

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

Usage Guidelines3/5

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

Usage is only implied: the tool is for keyword full-text search of the catalogue with optional filtering and pagination. There is no explicit statement of when to choose this over search_within, package, or organizations, and no when-not-to-use guidance.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.