Skip to main content
Glama

Your canaries, their state and their fires (operator session required)

canary_status
Read-onlyIdempotent

Needs a Desk session (Authorization: Bearer); without one this returns 401. Every canary you registered, with the watcher's last reading (nonce, code, balance, checks) and the newest 20 events per canary (trigger, severity, evidence, whether you declared it a test, the reading in plain words and what to do). Needs Authorization: Bearer . Labels are your own text and come back in the untrusted envelope.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, and the description adds real value beyond them: the exact 401 failure without a Bearer token, the 20-events-per-canary cap, and the fact that labels come back inside an untrusted envelope. That last point is a useful safety disclosure about prompt-injectable content. It stops short of 5 only because it does not say what happens past 20 events or how the results are ordered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The payload detail is front-loaded and dense, but the auth requirement is stated twice almost verbatim ("Needs a Desk session (Authorization: Bearer); without one this returns 401" and later "Needs Authorization: Bearer <Desk session>"). Removing the duplicate would tighten an otherwise efficient paragraph.

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 explaining returns and does so field by field (nonce, code, balance, checks; trigger, severity, evidence, test flag, plain-language reading, recommended action). Missing only the no-canaries case and ordering or paging behavior beyond the 20-event cap.

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 baseline of 4 applies; there is no parameter meaning left to explain.

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?

"Every canary you registered, with the watcher's last reading ... and the newest 20 events per canary" states the resource and contents concretely enough to act on. It does not contrast itself with siblings like canary_register, since_last, or self_check, so differentiation is left to the name.

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 usage is only implied by the name and returned payload (inspect registered canaries and their fires); there is no explicit statement of when to call this versus canary_register or another status tool. The only stated precondition is the Desk session.

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.