Skip to main content
Glama

Refresh data from CanadaBuys

refresh_data
Idempotent

Checks CanadaBuys for updated procurement data files, downloads changed versions, and replaces the local cache when search results need current data.

Instructions

Check CanadaBuys now for newer versions of every data file and download those that changed, replacing the local cache. Searches already refresh on their own schedule (new tenders every 2 hours, open tenders and this year's awards every 6, the rest daily); call this only when the user asks for the latest data or a search reported a refresh warning. It also downloads the award files if no award search has been run yet, which can take a minute.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare the safety profile (openWorld, idempotent, non-destructive); the description adds genuinely new behavior: the local cache is replaced, award files are downloaded when no award search has run yet, and the call can take a minute. That latency warning and the cache-replacement consequence are exactly the context annotations cannot convey.

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?

Three sentences, front-loaded with the action and immediately followed by the call/no-call rule. The parenthetical refresh cadences are dense but they are what justifies the 'only when' rule, so they earn their place; the sentence is slightly overloaded but nothing is redundant.

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

Completeness5/5

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

For a zero-parameter, no-output-schema tool with rich annotations, the description covers the trigger conditions, side effects, latency, and interaction with sibling search tools. There is no gap an agent would need to guess at before calling it.

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?

Zero parameters, so there is no parameter semantics to explain; the description correctly avoids inventing arguments and notes the implicit side effect of pulling award files. Nothing further is required for a no-argument tool.

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?

States a specific verb and resource ('Check CanadaBuys ... download those that changed, replacing the local cache') and distinguishes itself from the search siblings by explaining that searches refresh on their own schedule. An agent can tell exactly what this does versus search_tenders or data_status without opening any schema.

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

Usage Guidelines5/5

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

Explicit gating: 'call this only when the user asks for the latest data or a search reported a refresh warning,' plus the automatic refresh cadences that make a manual call unnecessary. It gives both the when and the when-not, which is the strongest form of guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.