Skip to main content
Glama
Sign In

Sautikit

by io.github.SautiKit
OverviewDiscussionsAdmin

test_webhook

Send a signed sample delivery to a webhook endpoint (safe: fabricated payload, no real event). Returns the delivery_id to check with list_webhook_deliveries.

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": "test_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadNocustom payload; omit for a canned sample
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.
event_kindNoevent kind to fabricate a sample for; only workspace-subscribable events are accepted (see create_webhook's events field) — call.* lifecycle events are rejected
webhook_idYeswebhook subscription UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare destructiveHint=false and openWorldHint=false, so safety is partly covered. The description adds real value beyond this by explaining that the payload is fabricated and no real event fires, and it discloses the delivery_id return so the agent knows to verify the result. It does not mention permission requirements or whether the call is synchronous, which slightly caps the score.

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 sentences with no filler; the safety qualifier is front-loaded before the follow-up instruction. Every clause carries information the agent needs to act.

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?

With no output schema, the description appropriately explains the delivery_id return value and points to the verification tool. Some gaps remain about auth and behavior on failure, but for a four-parameter test tool it covers what is needed.

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 coverage is 100%, so every parameter (webhook_id, payload, purpose, event_kind) already has its own description, including the rejection of call.* lifecycle events. The description adds no parameter-level detail beyond the schema, 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?

The description names a specific verb and resource ('send a signed sample delivery to a webhook endpoint') and immediately qualifies the scope ('fabricated payload, no real event'). That detail separates it from create_webhook, update_webhook, and retry_webhook_delivery without the agent needing to open another schema.

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?

The parenthetical clarifies when this is appropriate: testing an endpoint without triggering a real event. It also gives a follow-up path ('check with list_webhook_deliveries'). However, it never explicitly excludes alternatives such as retry_webhook_delivery or desk_test_webhook, so the agent must infer the boundary.

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