Skip to main content
Glama

Show data status

data_status
Read-onlyIdempotent

Reports cached CanadaBuys files, record counts, publication dates, and last check times to show how current the local procurement data is without downloading anything.

Instructions

Report which CanadaBuys files are loaded in the local cache, how many records each holds, when the source published them and when they were last checked. Use it to tell the user how current the data is. Does not download anything.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description usefully confirms read-only behavior ("Does not download anything") and enumerates the reported fields, but adds nothing about caching semantics, staleness thresholds, or failure modes when no files are loaded.

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?

Two sentences, front-loaded with what is reported and back-loaded with the use case and the negative constraint. No redundant restatement of the title and nothing that could be cut without losing meaning.

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?

With no output schema, the description carries the return-value burden and does so: file list, record counts, source publication time, and last-checked time. For a zero-argument read-only status tool, that is everything an agent needs to call it correctly.

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?

The tool takes zero parameters, so the schema imposes no semantic burden and the baseline is 4. The description's enumeration of returned fields is a bonus rather than compensation for missing parameter detail.

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: reports which CanadaBuys files are in the local cache, with record counts and publication/check timestamps. It also distinguishes itself from the refresh path with "Does not download anything," so an agent can separate it from refresh_data without opening a schema.

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

Usage Guidelines4/5

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

Gives a clear use case ("tell the user how current the data is") and an explicit exclusion ("Does not download anything"), which implicitly routes download/update needs elsewhere. It stops short of naming refresh_data as the alternative, so the routing is inferred rather than stated.

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