Skip to main content
Glama
ForgingStack Watchtower

ForgingStack Watchtower

by jdkabattles

get_watch

Fetch a watch by ID to view its current status (healthy, overdue, alerted, or snoozed) and the last 20 events for monitoring and troubleshooting.

Instructions

Fetch a watch by id, with its current status (healthy, overdue, alerted, snoozed) and its last 20 events.

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

Input Schema

NameRequiredDescriptionDefault
watch_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does valuable work by specifying the return payload, listing the four status values and stating that exactly the last 20 events are included (implying a fixed cap with no pagination). It says nothing about read-only safety, permissions, or what happens when the watch_id is unknown or invalid.

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?

One sentence, front-loaded with the operation and immediately followed by the return content. Every clause (status, its values, the 20-event cap) earns its place with no filler.

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 and no annotations, the description correctly spends its budget explaining the return value, including the fixed 20-event window and status enumeration, which is what a caller most needs. It is only slightly incomplete on error behavior and whether the events are ordered or truncatable.

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% and the single watch_id parameter is typed only as an integer. The description's 'by id' conveys that the parameter is a watch identifier, which is genuine but minimal added meaning. It does not clarify the expected id format, source, or validity range.

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 uses a specific verb and resource ('Fetch a watch by id') and goes on to name exactly what comes back: current status with its four enumerated values (healthy, overdue, alerted, snoozed) and the last 20 events. That clearly separates it from create_watch and the unrelated get_credits/get_receipt siblings. It stops short of a 5 only because it never explicitly contrasts itself with any sibling.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named. The only steer is implicit: you need a watch_id, so this is a lookup-by-identifier rather than a search or list operation. An agent must infer that from the phrasing.

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

Deploy Server

Other Tools