Skip to main content
Glama

RegMap Canada

Search internal trade barriers

search_barriers
Read-onlyIdempotent

Find interprovincial trade barriers in RegMap's inventory by occupation, product or sector (e.g. 'nurse', 'wine shipping', 'trucking'), optionally for a province pair (from -> to) or one jurisdiction. Returns plain-language question, short answer, who imposes it, and the regmap.ca URL to cite. For verified province-by-province barriers with from and to, also returns the status for that move.

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_barriers"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoDestination jurisdiction.
fromNoOrigin jurisdiction (where the person, product or firm comes from).
limitNoMax results (default 10, max 25).
queryNoOccupation, product, activity or sector in plain words.
topicNoRestrict to one barrier topic.
jurisdictionNoA single jurisdiction to filter by, instead of a pair.
include_historicalNoAlso return removed or resolved barriers (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 declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: it enumerates the returned fields (plain-language question, short answer, imposer, regmap.ca citation URL) and discloses a conditional result — the per-move status only appears for verified province-by-province barriers when both from and to are supplied.

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?

Three sentences, no filler, with the core resource and search dimensions front-loaded and the return-shape and conditional-status details following in order of decreasing importance. Every clause carries information an agent would otherwise have to guess.

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 seven optional parameters, the description carries the return-value burden well by naming the four returned fields and the conditional status field. Minor gaps remain: it does not say what happens when query is omitted entirely (unfiltered listing?) and does not mention the default result cap or pagination behavior.

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?

With 100% schema coverage, the baseline is 3, but the description goes further by giving exemplar query strings and clarifying that 'from -> to' is a directed origin/destination pair while jurisdiction is a single-jurisdiction alternative. The topic enum and include_historical flag are left entirely to the schema, but the pair-versus-single semantics are meaningfully enriched.

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 a specific verb and resource ('Find interprovincial trade barriers in RegMap's inventory') and backs it with concrete query examples ('nurse', 'wine shipping', 'trucking'), so the agent knows exactly what domain this tool covers. It does not explicitly contrast itself with siblings such as search_regulations or get_barrier, so the boundary between this and neighboring lookup tools is left to inference.

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 well: it explains that a province pair (from -> to) or a single jurisdiction are optional refinements of a topical search. But there is no explicit when-to-use-this-vs-alternative guidance, no statement of when a pair is preferred over a single jurisdiction, and no mention of when to prefer get_barrier for a known barrier.

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