Skip to main content
Glama

RegMap Canada

What RegMap covers

regmap_overview
Read-onlyIdempotent

Coverage counts, freshness dates, and the valid jurisdiction codes, barrier topics, regulation categories and sectors.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds useful context about what information is covered, including freshness dates and valid codes, but it does not describe return structure or other behavioral details. With rich annotations, this is adequate but not especially strong.

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?

The definition is a single compact sentence fragment with no wasted words, and the most important contents are front-loaded. The lack of a verb slightly weakens structure, but conciseness is strong.

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?

For a simple zero-parameter read-only overview with no output schema, the description gives enough information about what the tool covers. It could be more explicit about return shape or use, but the enumerated contents and annotations make it callable without confusion.

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

Parameters4/5

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

The tool has zero parameters, so there is no parameter semantics to explain. The baseline for a no-parameter tool is 4, and the description does not need to add anything here.

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 enumerates the specific content the tool provides: coverage counts, freshness dates, jurisdiction codes, barrier topics, regulation categories, and sectors. This makes the overview purpose clear, although it is a noun-phrase list rather than an explicit verb+resource statement. It is distinguishable from sibling tools like search_regulations or get_regulation by its coverage-meta focus.

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

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description offers no when-to-use guidance, no exclusions, and no alternatives. An agent could infer it is useful for discovering valid codes or data freshness, but the definition never states that. This is essentially no usage guidance.

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