Skip to main content
Glama

create_merchant_credential_rotation_challenge

Begin recovery of a lost merchant API key. Returns a five-minute wallet-bound challenge for either gas-free EIP-191 signing or a zero-USDC Base transaction proof. The wallet signs or submits the action; 402Mob never signs for it.

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": {
      "wallet": "<wallet>"
    },
    "name": "create_merchant_credential_rotation_challenge"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the five-minute expiry, the wallet binding, the two mutually exclusive proof mechanisms, and the non-custodial guarantee ("402Mob never signs for it"). It omits error/expiry handling and whether existing keys remain valid during recovery.

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 tight sentences, front-loaded with the action, then the return value, then the trust boundary. No filler, and the security-relevant caveat is placed last for emphasis.

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?

There is no output schema, so the description is obligated to explain the return value, and it does: a time-boxed, wallet-bound challenge with two submission forms. The remaining gap is the handoff to the completion tools and the meaning of the wallet parameter, but for a one-parameter challenge-issuing tool this is close to complete.

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 single parameter is documented only by the schema's regex pattern. The description's phrase "wallet-bound" hints that the wallet address scopes the challenge, but it never states whose wallet (the merchant's current authorized wallet vs. a new one) or that it must match the recovery request.

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?

"Begin recovery of a lost merchant API key" pairs a specific verb with a specific resource, and "Returns a five-minute wallet-bound challenge" clarifies the output. It implicitly delineates the two downstream paths (EIP-191 signing vs. Base transaction proof) that map to the complete_*_signature / complete_*_transaction siblings, though it never names 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?

The description makes clear this is the entry point of a recovery flow and that the wallet must subsequently sign or submit, which implies the correct sequencing. However, it never states when not to use it, that it must be followed by a specific completion tool, or what to do if the challenge expires.

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