Skip to main content
Glama

RegMap Canada

Compare provinces for a sector

compare_provinces
Read-onlyIdempotent

Rank the 13 provinces and territories by how many business-relevant acts and regulations they have for one sector (regulatory surface, not burden), with the federal count for reference.

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": {
      "sector": "<sector>"
    },
    "name": "compare_provinces"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectorYes
include_economy_wideNoAlso count rules that bind every business (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds real context beyond them: the unit being counted (acts/regulations per sector), the interpretive caveat that this is surface not burden, and that a federal reference count accompanies the provincial ranking. With no output schema, it stops short of describing ordering or output shape.

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 front-loaded sentence with the metric and scope stated first. The parenthetical and federal-reference clause earn their place by preventing misinterpretation, though the sentence is dense enough to be slightly hard to parse in one pass.

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 two-parameter read-only tool with no output schema, the description is nearly sufficient: it names the ranking dimension, the geographic universe, and the federal benchmark. It omits sort order and result shape, which are minor for a simple comparison call.

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 50%: the sector enum self-documents its 16 allowed values and include_economy_wide carries its own description. The description reinforces single-sector scope but adds nothing about how include_economy_wide changes the comparison, so it neither compensates for nor extends the schema meaningfully.

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?

Specific verb+resource: ranks the 13 provinces/territories by count of business-relevant acts and regulations for one sector. It also preempts misreading by stating 'regulatory surface, not burden' and noting the federal count is included for reference, which clearly separates it from lookup-style siblings like get_regulation or search_regulations.

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 the framing: a single-sector, cross-province comparison with a federal benchmark. There is no explicit when-to-use vs when-not guidance and no named alternative (e.g., regmap_overview) for agents deciding between aggregate views.

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