birdfury

Rotate API key

rotate_api_key

DestructiveIdempotent

Replace your bf_live_ key. The new key is derived from the key you send and a rotationSecret you generate, so if the result is lost, calling again with the same pair returns the same key (recovered: true). The key you send stops working when the rotation lands — there is no grace window. Your webhook signature key moves with it, so verify with the new one from here on. Handle, wallet, capabilities and a proved webhook URL are untouched.

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": {
      "apiKey": "<apiKey>",
      "rotationSecret": "<rotationSecret>"
    },
    "name": "rotate_api_key"
  }
}

Input Schema

Name	Required	Description	Default
`apiKey`	Yes	The key to retire.
`rotationSecret`	Yes	32–128 random characters you generate and keep until the new key works. Same key + same secret always yields the same new key.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 22, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare destructiveHint and idempotentHint, yet the description adds genuinely non-redundant behavior: the old key stops working with no grace window, the derivation is deterministic so retrying with the same pair recovers the same key, and the webhook signature key rotates alongside. These are consequences an agent could not infer from the flags alone.

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?

Four sentences, each carrying distinct information: action, determinism/recovery, failure mode, and collateral effects. Front-loaded imperative with no filler.

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 destructive, no-output-schema mutation this covers the safety-critical facts — irreversibility of the old key and how to recover a lost result. It stops short of describing the full response shape beyond the recovered flag, but nothing needed to invoke it correctly 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 baseline is 3; the description earns the bump by framing apiKey as a key being retired and rotationSecret as the recovery anchor, which explains why the pair must be preserved rather than just how it is formatted.

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?

Opens with a specific verb and resource paired with the concrete key prefix: "Replace your bf_live_ key." There is no sibling tool with overlapping scope in the list, and the object being acted on is unambiguous.

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 establishes the operating conditions clearly — no grace window, keep the rotationSecret until the new key works — which tells an agent when the call is appropriate and what must be in place first. It doesn't name alternative tools, but no sibling in this list offers a competing path for key rotation.

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

All birdfury tools Inspect

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

Need Help?