Skip to main content
Glama

claim

Request recovery of a lost token by submitting your fingerprint, agent label, and note; the request stays pending until the owner approves it.

Instructions

POST /wake/v1/claim. Request recovery of a lost token using the fingerprint given at register. Required: fingerprint, agent_label, note (≤2000). Returns 202 with pending claim token (401 claim_pending until owner approves). Limit: 1 per fingerprint per UTC day. Auth: none.

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": {
      "fingerprint": "<fingerprint>",
      "agent_label": "<agent_label>",
      "note": "<note>"
    },
    "name": "claim"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYes
agent_labelYes
fingerprintYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full behavioral burden and does so well: auth is none, the response is 202 with a pending claim token, subsequent calls return 401 claim_pending until owner approval, and there is a per-day rate limit. What is missing is what happens if the owner rejects, or whether a pending claim blocks other operations.

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?

Three short sentences plus a fragment, front-loaded with method, path, and purpose, then requirements, then return semantics and limits. No filler; every clause carries operational information.

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?

An output schema exists, so return values need not be detailed, yet the 202/pending-token behavior is summarized usefully. Auth, rate limit, and required fields are all covered; only rejection handling and the semantics of agent_label are 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 0%, so the schema only names the three required fields with no meaning. The description identifies all three as required and adds the key constraint that the fingerprint is the one from register plus a length cap on note (≤2000). It adds no detail on what agent_label is for or the expected note content.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Request recovery of a lost token using the fingerprint given at register.' The endpoint path and the register cross-reference make it distinguishable from siblings like register and get_capsule without opening schemas.

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?

Gives a clear precondition (fingerprint must be the one given at register) and the consequence of calling it while a claim is pending (401 claim_pending until owner approves). It also bounds frequency (1 per fingerprint per UTC day). It stops short of naming an explicit alternative for someone who has not registered, so no exclusions are stated.

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