Skip to main content
Glama

recover_management

Recover lost management after verified USDC payment. Challenge, sign the exact message with the actual paying wallet, then recover. No funds move. Public URLs and transaction hashes alone cannot claim ownership. EOA and ERC-1271 verification use the same public-chain verifier.

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": {
      "action": "<action>",
      "purchaseId": "<purchaseId>",
      "payer": "<payer>",
      "transactionHash": "<transactionHash>"
    },
    "name": "recover_management"
  }
}

Input Schema

NameRequiredDescriptionDefault
nonceNo
payerYes
actionYes
expiresAtNo
signatureNo
purchaseIdYes
transactionHashYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that no funds move, that ownership cannot be claimed from public URLs or transaction hashes alone, and that EOA and ERC-1271 verification use the same public-chain verifier. It still does not explain what management is being recovered or whether recovery is final, but it meaningfully extends the safety profile already supplied by annotations.

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?

The description is front-loaded with the core purpose and then proceeds logically through the workflow, safety caveat, and verification detail. Every sentence contributes useful information without unnecessary 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 complex two-step mutation tool with 7 parameters and no output schema, the description covers the high-level workflow and a key security restriction. It is still incomplete because required purchaseId and challenge-related nonce/expiresAt usage are not explained, and failure or return behavior is not described.

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?

The description maps the action values to challenge and recover, identifies payer as the actual paying wallet, and explains that signature signs the exact message, while transactionHash alone is insufficient to claim ownership. However, with 7 parameters and 0% schema description coverage, it leaves required purchaseId and optional nonce/expiresAt semantics unexplained.

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 states a specific verb and resource: recover lost management after verified USDC payment. It also distinguishes the two-step challenge/sign/recover process from a simple payment lookup, though it does not explicitly contrast with any sibling tool.

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?

It gives a clear prerequisite and ordered workflow: after verified USDC payment, challenge, sign the exact message with the actual paying wallet, then recover. It also warns that public URLs and transaction hashes alone cannot claim ownership, but it does not name alternative tools or when-not-to-use conditions.

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