Skip to main content
Glama

Rotate this key

rotate_key
Destructive

Replace the secret of the key making this request, keeping its name, scopes, allowance and history. The new key is in the response, shown once; the old one stops working immediately. Use it when a key may have leaked. (POST /api/v1/me/key/rotate)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rotate_key"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well past the annotations by disclosing that the old secret stops working immediately, that the replacement is returned only once in the response, and that metadata is carried over. These are exactly the consequences an agent must know before invoking an irreversible mutation, and the description supplies them without restating destructiveHint or idempotentHint.

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, front-loaded with the operation and its preserved fields, followed by the critical one-time-return warning and the usage cue. The endpoint annotation is appended parenthetically without crowding the substance; no sentence is filler.

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 zero-parameter, no-output-schema mutation, the description covers everything an agent needs: what changes, what survives, what is returned and how transient it is, and when to reach for it. Nothing material is left unstated.

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 tool takes no parameters, so there is nothing for the description to disambiguate. Baseline for a zero-parameter schema applies, and the description correctly avoids inventing inputs.

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 ('Replace the secret of the key making this request') and pins the scope as the caller's own key, which separates it from a general key-management tool. It also enumerates what is preserved (name, scopes, allowance, history), so an agent knows exactly what the operation does and does not change.

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 an explicit trigger: 'Use it when a key may have leaked.' That is clear context for invocation, but it offers no exclusion or contrast with the sibling revoke_key, so an agent must infer on its own that this tool is for continuity-preserving rotation rather than termination.

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.