Skip to main content
Glama
Sign In
RCA-MCP Connector

RCA-MCP Connector

by dave1362
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

rca_auth_rotate_key

Destructive

Deactivate an existing API key and generate a replacement for the same account in one call. Use to rotate compromised or expiring keys without losing access.

Instructions

Deactivate one of your existing API keys and generate a replacement for the same account in one call. Requires the multi-key feature (Pro plan or above -- up to 5 keys on Pro, unlimited on Enterprise).

Use rca_auth_list_keys first to find key_id if you don't already have it. Prefer this over rca_auth_revoke_token when you want a like-for-like replacement key in one step rather than just shutting the old one off.

Args: params (RotateKeyInput): - key_id: UUID of the existing key to deactivate (from rca_auth_list_keys), not the raw key string itself

Returns: str: JSON with old_key_id, new_key_id, api_key (new raw key -- store it now, it cannot be recovered later)

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": {
      "params": "<params>"
    },
    "name": "rca_auth_rotate_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv4.1.16
    • changedInput schema / $defs / RotateKeyInput / properties / token / description
      Previous value: -"API key (admin role required)"New value: +"API key to authenticate this request"
  2. Changed1 schema field changedv4.1.15
    • addedInput schema / $defs / RotateKeyInput / properties / client_id / description
      Added value: +"Client namespace ID"
  3. First observedv4.1.13

TDQS

A4.9/5.0
Behavior5/5

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

Beyond destructiveHint, the description discloses that the old key is deactivated and that the new raw api_key is returned only once and cannot be recovered later. This one-time-recovery warning is essential and not conveyed by the 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 definition is front-loaded with the core operation, followed by prerequisites, usage guidance, and input/output details. Each section earns its place and there is no 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 destructive auth operation, it covers the multi-key feature prerequisite, how to get key_id, the response shape, and the cannot-recover-later constraint. An agent has enough context to select and invoke this tool correctly.

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 description adds valuable semantics for key_id: it is a UUID from rca_auth_list_keys, not the raw key string. The other parameters are covered by the input schema, and the return description ties the result back to the parameters clearly.

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 first sentence states a specific action on a specific resource: deactivate an existing API key and generate a replacement in one call. It also distinguishes itself from rca_auth_revoke_token, making its purpose unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit prerequisite and workflow: use rca_auth_list_keys first to obtain key_id. It also tells the agent exactly when to prefer this tool over rca_auth_revoke_token, which is clear routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools