Skip to main content
Glama
Sign In

Sautikit

by io.github.SautiKit
OverviewDiscussionsAdmin

desk_retry_webhook_delivery

Sends one failed webhook delivery 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": {
      "webhook_id": "<webhook_id>",
      "delivery_id": "<delivery_id>"
    },
    "name": "desk_retry_webhook_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
webhook_idYeswebhook endpoint UUID
delivery_idYesdelivery UUID from desk_list_webhook_deliveries

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare openWorldHint=true and destructiveHint=false, so the agent knows this is a non-destructive action against an external endpoint. The description adds the useful scoping detail that exactly one delivery is retried. It does not say whether a new delivery record/id is created, whether retries are limited or rate-limited, or what the caller gets back.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler or restatement of the title. It is tight but so terse that it borders on under-specification rather than maximizing useful density.

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 simple two-identifier mutation with full schema coverage and annotations, the description is minimally adequate. It leaves out outcome information (new delivery vs. re-send on the same record) and any retry-limit or failure-handling context, which matters for an open-world side-effecting call with no output schema.

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%: webhook_id and delivery_id are documented, including that the delivery id comes from desk_list_webhook_deliveries. The description adds no meaning beyond that, so baseline 3 applies.

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?

States a specific verb+resource: re-sends one failed webhook delivery, retry semantics in one phrase. It implicitly distinguishes from desk_test_webhook and desk_list_webhook_deliveries but never names a sibling explicitly.

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?

The qualifier 'one failed' implies the precondition that the delivery must have failed, and 'again' implies retry rather than test. There is no explicit when-not guidance, no mention of desk_test_webhook as the alternative for confirming an endpoint works, and no note on prerequisites such as webhook being active.

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