Skip to main content
Glama

Register an intent with a verification probe (paid, x402)

deadman_register

PAID: dead-man switch for an irreversible action: register the intent, a lease and a probe; confirm in time or we run the probe and publish the verdict. Unpaid, it returns the price; pay with x402 (USDC on Base, Solana, Polygon, Arbitrum, Avalanche, Sei or X Layer) in _meta['x402/payment'] and call again. Feedback: POST /feedback (free). Read daily; no individual reply. Price: $0.0100 USDC.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "deadman_register"
  }
}

Input Schema

NameRequiredDescriptionDefault
probeNoAt least one of expectedBodyContains / expectedStatus is required.
descriptionNoWhat you are about to do.
leaseSecondsNoHow long before an unconfirmed entry's probe runs. 1..604800 seconds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / required
      Removed value: -[
      -  "description",
      -  "leaseSeconds",
      -  "probe"
      -]
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare the safety profile (not read-only, not destructive, closed-world), but the description supplies genuinely new behavioral facts: the price ($0.0100 USDC), the accepted payment rails, the x402 handshake, and the consequence of missing the deadline (probe runs, verdict is published). The feedback channel and no-reply policy are also disclosed. Minor tension exists with openWorldHint=false, since the probe later GETs an arbitrary external URL, but the registration call itself need not make that request, so it is not a true contradiction.

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?

The dead-man-switch mechanism and the PAID marker are front-loaded, and the payment instructions follow in logical order. The feedback sentence and 'Read daily; no individual reply' are mildly peripheral but short and genuinely informational. No padding or repetition.

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 3-parameter tool with a nested probe object and no output schema, the description covers the trigger, the price and the payment path well. The key gap is the confirm step: it says 'confirm in time' but never identifies which tool or endpoint performs that confirmation, which is the single most important follow-up action for a dead-man switch. Where the verdict is published is also left implicit.

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 100%, so url, expectedStatus, expectedBodyContains, description and leaseSeconds are already fully documented in the schema. The description only echoes the three top-level inputs as a list ('the intent, a lease and a probe') without adding format, default, or interplay guidance. Baseline 3 is appropriate when the schema does the heavy lifting.

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 and resource plus the mechanism: register an intent, a lease and a probe, with a dead-man switch that fires the probe and publishes a verdict if unconfirmed. That is far more than a restatement of the name. It stops short of a 5 because it never contrasts itself with plausible siblings such as watch_register or attest_create, so the agent must infer the boundary.

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?

Usage context is clear: it is for irreversible actions, and the payment loop is spelled out precisely (unpaid call returns the price, pay via _meta['x402/payment'] with USDC on the listed chains, then call again). No when-not-to-use condition or named alternative is given, which keeps it out of 5 territory.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources