Skip to main content
Glama

run_watcher

Run a watcher now to retrieve its check result. Optionally send the notification if it fires; by default it records the value as the new baseline without notifying.

Instructions

Run a watcher now and return what its check produced. Set notify to true to send the notification if it fires; by default this is a dry run that still records the value as the new baseline.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
notifyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does meaningful work: it discloses that the default is a dry run and, crucially, that even a dry run 'records the value as the new baseline' — a non-obvious side effect an agent must know before invoking. It does not mention permissions, rate limits, or whether the watcher's scheduling state is altered.

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, both front-loaded with the essential information: what it does first, then the notify/dry-run semantics. No filler and nothing redundant.

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?

For a two-parameter tool with no output schema, the description covers the mutation semantics and the return ('what its check produced') adequately. It could go further in describing what a check result looks like, but nothing essential for correct invocation is missing.

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 description coverage is 0%, so the description must compensate for both parameters. It explains 'notify' well (true sends the notification if it fires, default is dry run), but says nothing about 'name' — presumably the watcher identifier — leaving the caller to infer its meaning from the tool name.

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?

The description pairs a specific verb ('Run') with a specific resource ('watcher') and adds the outcome ('return what its check produced'), so the operation is unambiguous. It does not name any sibling (list_watchers, save_watcher, delete_watcher), though 'run ... now' implicitly contrasts with scheduled execution.

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?

It gives clear operational context: default behavior is a dry run, and setting notify=true is the condition for actually firing a notification. It stops short of naming any alternative tool or exclusion, which is the only thing separating it from a 5.

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