Skip to main content
Glama

Opendata Canada

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Package

package
Read-onlyIdempotent

Dataset by id/slug.

Input Schema

NameRequiredDescriptionDefault
idYes

Output Schema

NameRequiredDescriptionDefault
idNoPackage ID
urlNoPackage URL
nameNoPackage name/slug
tagsNoArray of tags
notesNoPackage description
titleNoPackage title
authorNoPackage author
groupsNoArray of group/theme objects
privateNoWhether package is private
versionNoPackage version
owner_orgNoOwner organization ID
resourcesNoArray of resources
license_idNoLicense ID
maintainerNoPackage maintainer
author_emailNoAuthor email
organizationNoOrganization object
maintainer_emailNoMaintainer email
metadata_createdNoCreation timestamp
metadata_modifiedNoModification timestamp

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "id": "air-quality-data"
-  }
-]New value: +[
+  {
+    "id": "5cf10ac5-f426-41b8-bf3a-43bd0721472f"
+  }
+]
    • changedOutput schema / properties / author / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / author_email / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / maintainer / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / resources / items / properties / description / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / resources / items / properties / last_modified / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / url / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / version / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
  2. Changed2 schema fields changed
    • 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"
+}
  3. First observed

TDQS

D1.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered by structured data. The description adds nothing beyond this—no information on error behavior for invalid ids, performance characteristics, or what 'package' actually is.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single, extremely short fragment. While it is concise, it is under-specified rather than appropriately sized—conciseness should not come at the cost of usefulness.

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

Completeness2/5

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

With a single parameter, 0% schema description coverage, and an output schema already handling return values, the description still needs to explain what the tool retrieves and how to interpret the id. It does not.

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

Parameters2/5

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

Schema description coverage is 0% for the single 'id' parameter. The description mentions 'id/slug' which hints the parameter accepts both identifiers, adding marginal value, but the schema itself says only 'string'. A 2 is appropriate because the description doesn't clarify the expected format or whether slug lookup is actually supported.

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

Purpose2/5

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

The name 'package' plus the fragment 'Dataset by id/slug' does not state a specific verb or scope. It is essentially a minimal restatement, giving the agent almost nothing beyond the name to distinguish it from siblings like entity_profile, company_facts, or search.

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

Usage Guidelines1/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 versus alternatives. It doesn't say whether id and slug are interchangeable, what kind of dataset it returns, or how it relates to other resource-lookup tools.

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

All Opendata Canada toolsInspect
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.

Resources