Skip to main content
Glama

RegMap Canada

Get one act or regulation

get_regulation
Read-onlyIdempotent

One catalogue instrument by slug: title, citation, jurisdiction, enabling act, currency date, official text link, regmap.ca URL, and any internal trade barriers that cite it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_regulation"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesInstrument slug from search_regulations (e.g. 'on-1a2b3c4d5e6f').

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. The description adds genuinely new behavior information by disclosing the returned fields, notably that citing internal trade barriers are embedded in the result, which matters for a tool with no output schema.

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?

A single sentence, front-loaded with the lookup key and identifier, then a compact field list. No filler, no repetition of the title.

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 and a single parameter, the definition needs to convey what comes back, and the field enumeration does that adequately for a record-fetch tool. Minor gaps remain, such as behavior for an unknown slug (error vs. empty), which an agent might want to know.

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?

There is a single required parameter with 100% schema description coverage, and the schema already explains the slug format and points to search_regulations. The description adds only 'by slug', so the schema is doing the heavy lifting and the baseline of 3 applies.

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 states clearly that this returns a single catalogue instrument looked up by slug, and enumerates the fields included (title, citation, jurisdiction, enabling act, currency date, official text link, regmap.ca URL, citing barriers). That is more than a restatement of the name, but it never contrasts itself with sibling lookups such as get_barrier or search_regulations, relying on 'slug' alone to separate it.

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 only implied: 'by slug' plus the schema note that the slug comes from search_regulations suggests a search-then-fetch workflow. There is no explicit when-to-use or when-not-to-use statement and no naming of alternatives, so the agent has to infer the workflow from the parameter documentation.

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