Sautikit

desk_rotate_webhook_secret

Destructive

Replaces a webhook's signing secret. The old one stops working at once; the new one is in this reply only.

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": {
      "webhook_id": "<webhook_id>"
    },
    "name": "desk_rotate_webhook_secret"
  }
}

Input Schema

Name	Required	Description	Default
`purpose`	No	Required on tools that read data or reports; recommended on every tool. One sentence: what you are doing and why (for example "finding this caller's open ticket to answer them"). Building a report, dashboard, analytics or an export is a SautiDesk Pro feature done by the report tools, not by pulling records.
`webhook_id`	Yes	webhook endpoint UUID

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4/5.0

Behavior4/5

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

The annotations already flag destructiveHint=true and openWorldHint=false, and the description adds two facts annotations cannot convey: the old secret stops working at once (immediate, irreversible breakage for any consumer still signing with it) and the new secret is shown only once in the reply. It stops short of saying whether rotation causes delivery failures or needs specific permissions.

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, front-loaded with the action and followed immediately by the irreversibility warning. Nothing is padding; every clause carries operational weight.

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 single-target mutation with no output schema, the description covers the two things an agent most needs: the old secret dies instantly and the replacement is retrievable only from this response. Permission prerequisites and any effect on in-flight deliveries are the only meaningful omissions.

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?

Schema description coverage is 100%, so both parameters are already documented (webhook_id as endpoint UUID, purpose as the one-sentence rationale). The description adds no parameter-level meaning, so the baseline of 3 applies.

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: 'Replaces a webhook's signing secret.' That is clearly distinct from desk_update_webhook (modifies config) and desk_delete_webhook (removes the endpoint), so an agent can pick it out of the sibling list without opening the schema.

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

Usage Guidelines3/5

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

There is no explicit when-to-use clause, no mention of when NOT to rotate, and no reference to desk_update_webhook or create_webhook as alternatives. Usage is only implied by the word 'replaces' and the immediacy of invalidation, which an agent must infer.

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

All Sautikit 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?