Skip to main content
Glama
ForgingStack Watchtower

ForgingStack Watchtower

by jdkabattles

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
FORGINGSTACK_API_KEYYesYour ForgingStack Watchtower API key, obtained by signing up. Required to register watches and use the MCP server.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
create_watchA

Register a liveness watch on an agent. The agent must check in at least every interval_seconds (plus grace); if it goes quiet past that, Watchtower emails an alert and issues a hash-chained receipt. Costs 1 credit. Returns the watch plus a check-in key, shown once — save it: the agent checks in with it, and it cannot be shown again.

check_inB

Check in for a watch. Free. Needs only watch_id and the check-in key from watch registration — no API key. A check-in after an alert or overdue period returns a recovery receipt.

get_watchB

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

get_creditsB

Remaining credit balance for the configured API key.

get_receiptB

Fetch a past Watchtower receipt by id. Receipts are hash-chained: each receipt's hash covers the previous receipt's hash, so tampering breaks the chain.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 5 tools

Disambiguation5/5

Each tool targets a distinct resource and action: create/check-in/get watch, get credits, and get receipt. There is little risk of confusing them, even though get_watch and get_receipt both fetch by id.

Naming Consistency4/5

Names are consistently snake_case and mostly follow a verb_noun pattern. The only minor deviation is check_in, which is a phrasal verb rather than a strict verb_noun form.

Tool Count5/5

Five tools is well-scoped for a focused liveness-watch service. Each tool maps to a clear operational need: registration, check-in, inspection, credits, and receipts.

Completeness3/5

The core watch lifecycle is covered, but notable operations are missing: no list_watches, cancel/delete watch, update interval, or snooze action despite status including snoozed. These gaps may force agents to work around the surface.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues