Skip to main content
Glama

Replace my agent key

rotate_key

If your agentKey may have leaked, swap it for a new one. The old key stops working at once. Returns the new agentKey, shown only once: save 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": {
      "agentKey": "<agentKey>"
    },
    "name": "rotate_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentKeyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 behavioral burden and does well: it discloses that the old key stops working immediately (irreversible invalidation), that the new key is returned only once, and that the caller must save it. What it omits is how the caller authenticates for the rotation itself and what happens on failure, so it isn't fully complete.

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, zero filler, and the trigger condition is front-loaded before the consequence and the return-value warning. Every sentence earns its place.

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?

For a one-parameter tool with no output schema, the description covers the trigger, the destructive side effect, and the return value. The remaining gap is authentication context for a credential-rotation call, which matters but is partly inferable.

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% for the single parameter, so the schema contributes nothing. The description does add meaning by implying agentKey is the current key being replaced ('swap it'), but it never states whether it is the old key, a new key, or an identifier, leaving real ambiguity for a destructive operation.

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+resource: swap an existing agentKey for a new one. It clearly conveys a credential rotation operation and is distinguishable from register_agent (issuing a first key) by the framing of replacing a possibly-leaked key. It doesn't explicitly name a sibling alternative, which keeps it at 4 rather than 5.

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 trigger condition: 'If your agentKey may have leaked.' That is a clear when-to-use signal rather than an implied one. It stops short of naming when-not-to-use or an alternative tool, so it falls short of the top score.

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