Skip to main content
Glama
Sign In

RelayLink

by ai.relaylink
OverviewDiscussionsAdmin

Revoke an API key (irreversible)

revoke_api_key
DestructiveIdempotent

Turn off one API key, by the name the user gave it or by its id from list_api_keys. Anything still using it stops working on its next call, including possibly this connection — say which key you are about to revoke and let the user confirm before calling. Cannot be undone: a replacement is a new key. A notice goes to the account's email address.

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": {
      "key": "<key>"
    },
    "name": "revoke_api_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesThe key's name as list_api_keys shows it, or its id.

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?

Goes well beyond the annotations: warns that anything using the key stops working on its next call, that this may include the current connection, that revocation cannot be undone and a replacement is a new key, and that a notice is emailed to the account address. These are consequences an agent cannot infer from destructiveHint alone.

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?

Leads with the action, then the identifier forms, then the consequence and confirmation requirement. Dense but largely front-loaded; the emailed-notice clause trails slightly but still carries real information.

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?

One-parameter destructive tool with no output schema; the description supplies the blast radius, irreversibility, confirmation gate, and identifier source. Nothing an agent needs in order to call it safely is missing.

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?

Schema coverage is 100%, so the baseline would be 3, but the description adds sourcing semantics the schema lacks: the value is either the name as the user gave it or an id obtained from list_api_keys, which tells the agent where to get a valid input.

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 ('Turn off one API key') and immediately names the two ways to identify the target (user-given name or id from list_api_keys). An agent can distinguish this from list_api_keys without opening either schema.

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?

Explicitly prescribes a confirmation workflow: say which key is about to be revoked and let the user confirm before calling. It also points to list_api_keys as the source of valid identifiers. It stops short of naming a when-not-to-use condition, but the confirmation gate covers the practical risk.

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

All RelayLink toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources