Skip to main content
Glama

Vigil — an outside witness for AI agents

by com.vigilnotary
OverviewDiscussionsAdmin

vigil_delete_watchdog

DestructiveIdempotent

Remove a watchdog. Destructive: deletes its configuration and stops future alerts. No undo or restoration of the previous timer is provided.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesWatchdog name, 1..64 characters.
vigil_keyNoDEPRECATED legacy account-wide credential, including deletion and permission issuance. Prefer the client-injected HTTP Authorization: Bearer header; omit this argument when that header authenticates the request. This is not a scoped agent token.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / examples
      Added value: +[
+  {
+    "name": "agent-health"
+  }
+]
    • addedInput schema / properties / name / description
      Added value: +"Watchdog name, 1..64 characters."
    • addedInput schema / properties / name / maxLength
      Added value: +64
    • addedInput schema / properties / name / minLength
      Added value: +1
    • addedInput schema / properties / vigil_key / deprecated
      Added value: +true
    • changedInput schema / properties / vigil_key / description
      Previous value: -"Legacy credential argument. Prefer the HTTP Authorization: Bearer header; omit this argument when that header authenticates the request."New value: +"DEPRECATED legacy account-wide credential, including deletion and permission issuance. Prefer the client-injected HTTP Authorization: Bearer header; omit this argument when that header authenticates the request. This is not a scoped agent token."
    • addedInput schema / properties / vigil_key / maxLength
      Added value: +256
    • addedInput schema / properties / vigil_key / minLength
      Added value: +1
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already mark the tool as destructive, but the description adds valuable specifics: deleting the configuration, stopping future alerts, and no restoration of the previous timer. This goes beyond the structured annotations without contradicting them.

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 short sentences with no filler. The action is stated first, then the destructive consequences are front-loaded, and every clause earns its place.

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 simple delete operation with a fully documented two-parameter schema, the description covers the critical consequences an agent must know: configuration loss, stopped alerts, and irreversibility. The idempotent annotation further covers repeated calls, so nothing essential 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 100%, and the schema documents both parameters well, including the deprecated vigil_key guidance. The description adds no parameter-level detail, so the baseline of 3 is appropriate.

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?

The description opens with a specific verb and resource ('Remove a watchdog') and immediately clarifies the destructive scope: deletes configuration and stops future alerts. This clearly distinguishes it from siblings like vigil_set_watchdog and vigil_watchdog_status.

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?

The description gives clear usage context by warning that the operation is destructive, stops alerts, and has no undo. It does not explicitly name alternatives or state when-not-to-use, but the warning strongly implies caution and makes the tool's purpose unambiguous.

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

All Vigil — an outside witness for AI agents toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources