Skip to main content
Glama
Sign In

Sautikit

by io.github.SautiKit
OverviewDiscussionsAdmin

create_webhook

Create a webhook subscription. The response includes the signing secret ONCE — tell the user to store it now; it is never shown again.

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": {
      "url": "<url>",
      "events": "<events>"
    },
    "name": "create_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesHTTPS endpoint to deliver events to
eventsYesworkspace-subscribable event kinds only (call.* lifecycle events are NOT accepted here — they route per-number instead), e.g. broadcast.call.started, number.provisioned, wallet.low_balance
purposeNoRequired 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.
idempotency_keyNoclient-chosen key so a retried create does not mint a second webhook + second secret

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

The annotations only declare openWorldHint=false and destructiveHint=false, so the description carries the interesting burden and does so well by disclosing the one-time secret disclosure and the instruction to surface it to the user. That is exactly the non-obvious behavior an agent would otherwise miss and cannot recover from after the call.

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, zero filler, with the irreversible consequence front-loaded ahead of the softer instruction. Nothing could be removed without losing meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a create/mutation tool with annotations and no output schema, the description covers the critical trap (secret shown once) but is thin on the surrounding workflow. It never mentions the duplicate-creation protection from idempotency_key in prose, nor how this differs from desk_create_webhook or how to follow up with test_webhook.

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 url, events, purpose, and idempotency_key are already documented, including the event-kind restriction and the retry-safety rationale. The description adds only the response-side secret behavior and nothing extra about the parameters themselves, which fits the baseline of 3.

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 gives a specific verb and resource ("Create a webhook subscription"), so an agent immediately knows this mints a new subscription rather than modifying one. It does not differentiate itself from the closely named sibling desk_create_webhook, which is the one ambiguity an agent faces here.

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 guidance on when to use this over update_webhook, desk_create_webhook, or test_webhook, nor any stated prerequisites or exclusions. Usage is only implied by the verb "Create".

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

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