Skip to main content
Glama

RegMap Canada

Recent changes to the barrier inventory

recent_changes
Read-onlyIdempotent

What changed in RegMap's barrier inventory at recent refreshes: barriers added, amended, removed or restored.

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

Input Schema

NameRequiredDescriptionDefault
daysNoHow many refresh dates to return (default 5).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/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 safety adds nothing new. Beyond that the description only enumerates change categories; with no output schema it should explain how changes are returned (grouped by refresh date? ordered?), what a 'refresh' is, or any rate/recency limits, but it stays at the level of vocabulary.

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?

One sentence, front-loaded with the core question it answers ('what changed'), followed by the enumeration of change types. No filler, no restatement of the title, no wasted clauses.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a low-complexity read tool with one optional param whose schema is fully documented and annotations covering safety, the description covers the essential question. The gaps—return shape (no output schema exists), ordering, and what 'recent refreshes' represent—are real but secondary for a simple lookup.

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 100% and the single `days` parameter is already documented in the schema as 'how many refresh dates to return (default 5)'. The description adds nothing about the parameter—no mention of the 1–12 bound, default, or what a 'refresh date' means—so baseline 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?

States a specific resource (RegMap's barrier inventory) and scope (changes at recent refreshes), then enumerates the change kinds returned: added, amended, removed, restored. That is far more specific than the title, and it is distinguishable from siblings like search_barriers or get_barrier, which read current state rather than deltas—though the description does not name them explicitly.

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?

It implies usage (look here to see what changed) but gives no explicit when-to-use or when-not-to-use guidance, no prerequisites, and no pointer to alternatives such as search_barriers for current inventory state. An agent must infer the routing decision entirely.

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