Skip to main content
Glama
ForgingStack Watchtower

ForgingStack Watchtower

by jdkabattles

check_in

Submit a liveness check for a watch using its watch_id and check-in key; free and no API key, returning a recovery receipt after an alert or overdue period.

Instructions

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.

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>",
      "checkin_key": "<checkin_key>"
    },
    "name": "check_in"
  }
}

Input Schema

NameRequiredDescriptionDefault
watch_idYes
checkin_keyYes

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?

With no annotations, the description must carry the behavioral burden, and it does disclose several non-obvious traits: the call is free, it authenticates with a check-in key rather than an API key, and it returns a recovery receipt when the watch was in alert or overdue state. It omits idempotency, rate limits, error behavior for an invalid key, and whether the call resets the watch's timer or status.

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

Conciseness4/5

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

Three compact clauses, front-loaded with the action and cost, then the auth requirements, then the recovery behavior. Every clause carries information; only the recovery-receipt sentence feels partially appended rather than integrated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 and no annotations, the description covers inputs, auth, cost, and one notable return case. It leaves the normal (non-recovery) response and any effect on watch state unspecified, which is a meaningful gap for a state-changing operation.

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 coverage is 0%, so the description must supply the meaning, and it does name both parameters and give provenance for checkin_key (obtained from watch registration), which the schema does not convey. It gives no format or validation detail for the key, and watch_id is left as an obvious identifier with no further semantics.

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?

"Check in for a watch" gives a specific verb plus resource, and the follow-on clause about a recovery receipt clarifies what the operation means in the watch lifecycle. It is not tautological and is distinguishable from the sibling read tools (get_watch, get_receipt), though it never explicitly contrasts itself with them.

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?

Usage is implied rather than stated: the mention of "a check-in after an alert or overdue period" hints at when this is called, and the note about not needing an API key removes a common blocking question. There is still no explicit when-to-use vs. when-not guidance or reference to an alternative like get_receipt for inspecting state.

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