Skip to main content
Glama

New recovery code

new_recovery_code
Destructive

Make yourself a new recovery code, if the one you have may have been seen: send the one you have as recovery_code, with your key. The old one stops working at once, and the new one is shown this once. Your key stays as it is. A lost recovery code can't be replaced.

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": {
      "recovery_code": "<recovery_code>"
    },
    "name": "new_recovery_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoOnly if your app can't send an Authorization header: your API key, with every call. It then sits in this chat's transcript, so keep the transcript to yourself; if it may have been seen, your recovery code replaces it (POST /v1/recover). With a header, leave it out.
recovery_codeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, and the description goes further by naming exactly what is destroyed ("The old one stops working at once"), what is returned and its one-time visibility ("the new one is shown this once"), and what is unaffected ("Your key stays as it is"). For a credential-rotating mutation this is precisely the missing context an agent needs before calling.

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 trigger condition is front-loaded, and each subsequent sentence adds a distinct, load-bearing fact (old code revoked, new code shown once, key unchanged, lost code unrecoverable). The first sentence is a slightly tangled construction with the parameter instruction embedded mid-phrase, but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter destructive tool with no output schema, the description covers trigger, side effects, one-time return visibility, and irreversibility. There is no meaningful gap an agent would need filled before invoking it.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema documents the optional key parameter thoroughly but leaves recovery_code with no description at all, so the description does real work by explaining that recovery_code is the caller's current code. The only weakness is the unqualified "with your key," which reads as mandatory even though the schema says the key is only used when no Authorization header can be sent.

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?

The description uses a concrete verb and resource ("Make yourself a new recovery code") and immediately scopes the trigger condition ("if the one you have may have been seen"). No sibling tool in the list performs credential rotation, so no disambiguation is needed, but the operation is still unmistakable from the first clause.

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 an explicit when-to-use condition (the code may have been seen) and an explicit exclusion ("A lost recovery code can't be replaced"), which tells the agent when this tool is useless. What's absent is any pointer to an alternative path when the code is lost, though arguably none exists here.

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