Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Rotate webhook secret

rotate_webhook_secret
Destructive

Rotate a webhook endpoint's signing secret and return the endpoint with the new secret shown once, so you can replace compromised or outdated credentials and update integrations.

Instructions

Rotate a webhook endpoint's signing secret. Returns the endpoint and the NEW secret (shown only once).

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": {
      "id": "<id>"
    },
    "name": "rotate_webhook_secret"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.73.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / required
      Added value: +[
      +  "id"
      +]
  2. First observedv0.73.1

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the destructiveHint annotation, the description discloses a genuinely important operational trait: the new secret is returned and shown only once, which tells the agent to capture and persist it immediately. It does not state whether the old secret is invalidated instantly or whether a grace period exists, which would complete the destructive-behavior picture.

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?

Two short sentences with the action first and the return/one-time-secret caveat second; every clause carries information and there is 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 one-parameter destructive mutation with no output schema, the description covers what the tool does and what it returns, including the one-time visibility of the secret. Missing only secondary details such as permission requirements and whether the previous secret stops working immediately.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter 'id' has zero schema description coverage, so the description carries the burden. It implies the id identifies the webhook endpoint whose secret is rotated, which is partial compensation, but it never explicitly maps the parameter to that meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource (rotate a webhook endpoint's signing secret), so the action is unambiguous and clearly distinct from create/delete/update webhook siblings. It stops short of explicitly contrasting with update_webhook, but the operation itself is precisely stated.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no mention of update_webhook as the alternative for changing other endpoint properties. The agent must infer that rotation is for secret replacement only from the verb 'rotate'.

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