Skip to main content
Glama

RegMap Canada

Internal trade reform tracker

reform_status
Read-onlyIdempotent

Dated, officially sourced internal trade reforms since 2025 (laws passed or in force, regulations, agreements, exception removals, mutual recognition), filtered by jurisdiction, status or keyword, plus upcoming dates. Each event has its regmap.ca URL and official source.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 10, max 25).
queryNoKeyword, e.g. 'alcohol', 'labour mobility', 'trucking'.
sinceNoOnly events on or after this date (YYYY-MM-DD).
statusNo
jurisdictionNoJurisdiction code, or ALL for FPT-wide events only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and closed-world, so the safety profile is covered; the description adds genuinely new context on data provenance ('officially sourced', dated) and the coverage window (since 2025). The mention of 'upcoming dates' also signals that future-dated events are returned, which is not derivable from the schema or annotations.

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 dense sentence with the scope front-loaded before the parenthetical event types and the filter clause. The parenthetical list is long but each item is informative, and nothing is repeated.

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?

With no output schema, the description compensates by stating what each returned event carries (a regmap.ca URL and an official source) and confirming the temporal window. For a five-parameter filtered read tool with strong annotation coverage, nothing an agent needs to call it correctly is missing.

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

Parameters3/5

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

Schema coverage is 80%, so the schema already documents limit, query, since, status and jurisdiction. The description only echoes the filter dimensions and gives sample keywords indirectly ('alcohol' style terms live in the schema), adding no format or precedence rules such as how keyword matches interact with jurisdiction=ALL.

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 names the concrete resource (internal trade reforms since 2025) and enumerates the event types it covers (laws in force, regulations, agreements, exception removals, mutual recognition), so the agent knows exactly what comes back. It stops short of distinguishing itself from siblings like recent_changes or search_regulations, and the name 'reform_status' slightly suggests a single-record status lookup rather than a filtered list.

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?

The filter set (jurisdiction, status, keyword) implies the use case of narrowing a reform timeline, but there is no explicit when-to-use statement and no named alternative for overlapping needs such as recent_changes or compare_provinces. Usage is inferable rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources