Skip to main content
Glama

RegMap Canada

Get one barrier with sources

get_barrier
Read-onlyIdempotent

Full record for one internal trade barrier: summary, legal basis, the regulations it cites, official and study sources, review date, and for verified barriers the answer in every province and territory. Pass from and to for a province-pair answer.

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": {
      "id": "<id>"
    },
    "name": "get_barrier"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesBarrier id from search_barriers (e.g. 'dtc-alcohol', 'b63').
toNoJurisdiction code (CA = federal, BC, AB, SK, MB, ON, QC, NB, NS, PE, NL, YT, NT, NU) or its name.
fromNoJurisdiction 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.6/5.0
Behavior3/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world behavior, so the safety profile is fully handled elsewhere. The description adds genuine context that only a verified barrier carries a per-province answer set and a review date, but it never says what happens for unverified barriers or when the from/to pair returns no answer.

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?

Two sentences, front-loaded with the resource and its contents, then the optional-parameter rule. The field enumeration is dense but each item is meaningful; nothing is redundant filler.

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 carries the burden of describing the return, and it does so by listing the record's sections and noting the conditional provincial/territorial answers. Remaining gaps are minor — no mention of lookup failure behavior or record shape.

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?

Schema coverage is 100%, so the baseline is 3, and the description earns an extra point by explaining that from and to must be supplied together to get a province-pair answer — pair semantics the schema's per-field descriptions do not convey. It also indirectly ties the required id to records from search_barriers.

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?

Opens with a concrete verb+resource pairing ("Full record for one internal trade barrier") and then enumerates exactly what the record contains: summary, legal basis, cited regulations, official and study sources, review date, provincial/territorial answers. 'One' implicitly contrasts with the search/list sibling, but the description never names that sibling, so differentiation rests on the schema hint rather than the prose.

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?

The only guidance is "Pass from and to for a province-pair answer," which explains the optional-parameter mode but not when to pick this tool over alternatives such as compare_provinces or get_regulation. Usage is implied by the 'fetch one known record' framing rather than stated.

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