Opendata Canada

Package

package

Read-onlyIdempotent

Dataset by id/slug.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description
`id`	No	Package ID
`url`	No	Package URL
`name`	No	Package name/slug
`tags`	No	Array of tags
`notes`	No	Package description
`title`	No	Package title
`author`	No	Package author
`groups`	No	Array of group/theme objects
`private`	No	Whether package is private
`version`	No	Package version
`owner_org`	No	Owner organization ID
`resources`	No	Array of resources
`license_id`	No	License ID
`maintainer`	No	Package maintainer
`author_email`	No	Author email
`organization`	No	Organization object
`maintainer_email`	No	Maintainer email
`metadata_created`	No	Creation timestamp
`metadata_modified`	No	Modification timestamp

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 27, 2026

addedInput schema / examples

Added value: +[
+  {
+    "id": "air-quality-data"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "CKAN package details",
+  "properties": {
+    "author": {
+      "description": "Package author",
+      "type": "string"
+    },
+    "author_email": {
+      "description": "Author email",
+      "type": "string"
+    },
+    "groups": {
+      "description": "Array of group/theme objects",
+      "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"
+}

First observedMay 18, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. Description adds no behavioral context beyond this, but does not contradict annotations. Acceptable baseline given annotation coverage.

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?

At four words, the description is extremely concise and front-loaded. However, it may be too terse for a tool with no sibling differentiation, but given low complexity, it is acceptable.

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

Completeness3/5

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

With one simple parameter, strong annotations, and an output schema present, the description could be minimal. However, it lacks any mention of edge cases (e.g., id not found) or usage context, leaving it slightly incomplete.

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?

The input schema provides only a parameter name 'id' with no description. The description adds the crucial detail that 'id' can be an id or slug, which significantly aids agent understanding and correct usage.

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

Purpose3/5

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

Description states 'Dataset by id/slug' which clearly indicates retrieving a dataset by identifier. However, it is vague and does not differentiate from sibling tools like 'entity_profile' or 'resolve_entity'.

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?

No guidance on when to use this tool vs alternatives. No mention of prerequisites, when-not to use, or relationship to siblings.

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.