Skip to main content
Glama

RegMap Canada

Search Canadian acts and regulations

search_regulations
Read-onlyIdempotent

Search RegMap's catalogue of more than 25,000 federal, provincial and territorial acts and regulations (titles from official legislation portals) by keyword, jurisdiction, topic category or sector. Returns titles, citations, the official text link and the regmap.ca URL to cite.

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": "search_regulations"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResult page (default 1).
typeNoOnly acts or only regulations.
limitNoMax results (default 10, max 25).
queryNoKeywords, e.g. 'food premises', 'liquor licence'.
sectorNoIndustry sector.
categoryNoRegulatory topic category.
jurisdictionNoJurisdiction code (CA = federal, BC, AB, SK, MB, ON, QC, NB, NS, PE, NL, YT, NT, NU) or its name.

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 readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. Beyond that the description adds real value: it states that only titles (not full text) are searched, that titles come from official legislation portals, and exactly what each result contains (titles, citations, official text link, regmap.ca citation URL). It omits result-count and pagination behavior, which the schema only partially implies.

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?

Two sentences, front-loaded with the verb and scope, then the return contents. No filler, no repetition of the title, and every clause contributes either scope or output information.

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 no output schema, the description correctly takes on the job of explaining return fields and citation URLs, and annotations cover the read-only safety profile. For a 7-parameter, all-optional search tool the coverage is nearly complete; only pagination/result-count behavior and facet-combination semantics are left unstated.

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 description coverage is 100% with three enums fully enumerated, so the schema carries the parameter documentation. The description restates the four primary search facets (keyword, jurisdiction, category, sector) but adds no meaning beyond them, such as how facets combine or that limit caps at 25. Baseline 3 is appropriate.

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 and resource ('Search RegMap's catalogue of ... acts and regulations') plus concrete scope (25,000+ federal, provincial and territorial items). The parenthetical 'titles from official legislation portals' usefully narrows what is actually searched, which separates it from a full-text tool. It stops short of naming a sibling such as get_regulation for retrieving a single instrument's content, so the differentiation is only partial.

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 implied by listing the facets (keyword, jurisdiction, topic category, sector) you can search by, which tells an agent this is the discovery entry point. There is no explicit when-to-use/when-not guidance and no pointer to alternatives like get_regulation once a title is found. Adequate but leaves routing to the agent's inference.

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