Skip to main content
Glama

WhatsDownNow

Reset a stack's manage link

rotate_alert_stack_key

Replace a stack's management token and manage_link. The old token and link stop working immediately. Use this if the manage_link may have leaked. Returns the new token and manage_link once; give the new manage_link to the user privately. Counts toward the stack's daily change limit. Needs the stack id and its current management token. The stack itself is not deleted.

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": {
      "stack_id": "<stack_id>",
      "token": "<token>"
    },
    "name": "rotate_alert_stack_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesManagement token (wdn_...) returned once by create_alert_stack
stack_idYesStack id (stk_...) returned by create_alert_stack

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 beyond the annotations: states the old token and link stop working immediately, that the new values are returned only once and must be delivered privately, that the call consumes the stack's daily change limit, that the current management token is required for auth, and that the stack itself survives. This covers consequences, rate limits, credential handling, and the non-destructive scope that destructiveHint=false implies.

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?

Six short sentences, front-loaded with what changes, then consequences, then usage trigger, then return contract, then constraints. Every sentence carries information an agent needs; nothing is restated from the schema verbatim.

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 two-parameter credential-rotation mutation with no output schema, the description supplies the return contract, the one-time visibility of the secret, the invalidation effect, the auth requirement, and the rate-limit cost. No material gap remains for correct invocation.

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 is 3, but the description adds real disambiguation: the token parameter must be the *current* management token, not a new one, which is a genuine ambiguity in a rotate operation. It also confirms both parameters are mandatory 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?

Names a specific verb (Replace) and precise resources (management token and manage_link) on an identified object (a stack). The security-rotation framing separates it clearly from the general update_alert_stack sibling without needing to name it.

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 triggering condition: 'Use this if the manage_link may have leaked.' It does not name when-not to use it or point at the sibling that handles ordinary setting changes, but the condition is unambiguous enough to route most callers correctly.

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.