Skip to main content
Glama
Sign In

Opendata Canada

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Opendata Canada Groups

opendata_canada_groups
Read-onlyIdempotent

List the subject-area themes used across open.canada.ca (e.g. Nature And Environment, Science And Technology, Health And Safety), ranked by dataset count. Each theme includes an fq filter string to pass to the search tool to list that theme's datasets. Use this to browse what Canada publishes by topic before searching.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 15
    },
    "name": "opendata_canada_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
noteNoExplanatory note about the theme source
countYesNumber of themes returned
groupsYesThemes from the Solr `subject` facet.
total_datasetsNoTotal datasets across the portal

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real context beyond that: results are ordered by dataset count and each entry carries an fq filter string intended for the search tool, which tells the agent how to chain calls.

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?

Three tight sentences, front-loaded with the core action and ordering, then the output payload, then the usage instruction. The parenthetical theme examples earn their space by making the ranking concept concrete.

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?

An output schema exists, so return values need no explanation, and annotations cover safety; the description supplies the purpose, ordering and fq handoff an agent needs. The only material gap is the undocumented limit parameter, which affects how many themes the agent can request.

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?

There is one parameter (limit) with 0% schema description coverage, and the description never mentions it — no default, no maximum, no statement about how many themes come back. With low schema coverage the description was expected to compensate, and it does not.

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?

States a specific verb and resource ('List the subject-area themes used across open.canada.ca') plus the ordering rule ('ranked by dataset count') and concrete examples of theme names. It is clearly distinguishable from the search sibling because it says this returns themes, not datasets.

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?

Gives explicit sequencing guidance: 'Use this to browse what Canada publishes by topic before searching,' and explains the handoff via the fq filter string to the search tool. It does not state when NOT to use it (e.g. go straight to search when you already know the topic), so it stops short of a full routing rule.

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