Skip to main content
Glama
ForgingStack Watchtower

ForgingStack Watchtower

by jdkabattles

get_receipt

Fetch a past Watchtower receipt by ID to verify its hash-chain integrity and detect tampering.

Instructions

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.

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

Input Schema

NameRequiredDescriptionDefault
receipt_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/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 it does add one genuinely useful behavioral fact: receipts are hash-chained, so a returned receipt can be integrity-checked against its predecessor. It does not state whether the call is read-only, what happens for an unknown id, or what the response looks like.

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, front-loaded with the action and key, followed by one sentence of relevant domain context. No filler or redundancy.

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 one-parameter read tool with no output schema and no annotations, the definition covers the core action and adds integrity context, but omits the return shape, missing-id behavior, and any permission or scope notes. It is adequate but leaves real gaps an agent would want closed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 the single receipt_id parameter, but it only restates 'by id'. It never says where the id originates (e.g., from a check_in or create_watch response) or what form it takes beyond the schema's integer type.

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 names a specific verb (fetch) and resource (Watchtower receipt) plus the lookup key, which clearly separates it from siblings like get_credits, get_watch, and create_watch. It stops short of explicitly contrasting itself with those siblings, but the resource noun is distinctive enough for an agent to pick it correctly.

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 named alternative for related lookups. The only implied guidance is that the caller must already have a receipt id for a past receipt, which an agent must infer.

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