Skip to main content
Glama
Sign In
SetLuca

SetLuca

Official
by setluca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Send a test webhook

luca_webhooks_test_delivery
Destructive

Queue a canonical test webhook event.

Instructions

Queue a canonical test webhook event.

Luca operation: POST /api/webhook-subscriptions/test-delivery Required scopes: webhooks:write Required OAuth scope: luca:full; data sensitivity: redacted Requires Idempotency-Key. Provide idempotencyKey for safe retries, or the server will generate one. Destructive: has a real-world side effect. You must pass confirm: true; the call is rejected without it. Use workspaceId or workspaceSlug to override the default workspace configured by environment.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "luca_webhooks_test_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNo
confirmNoThis tool has a real-world side effect: it messages real leads, books, moves, or cancels a call, changes a lead's consent, imports leads, writes to a connected calendar or CRM, sends workspace events to an outside URL, or re-triggers downstream automations. Pass confirm: true to proceed; the call is rejected without it.
workspaceIdNoOptional Luca workspace id override.
workspaceSlugNoOptional Luca workspace slug override.
idempotencyKeyNoStable key for safe retries. If omitted, the MCP server generates a unique key for this call.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.4.1
    • addedInput schema / properties / body / properties / data / additionalProperties
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "object"
+    },
+    {
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • removedInput schema / required
      Removed value: -[
-  "body"
-]
  2. First observedv0.4.0

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the underlying operation (POST /api/webhook-subscriptions/test-delivery), required scopes, the intent scope and data sensitivity, the Idempotency-Key requirement with server-side generation fallback, and the hard confirm: true gate. These are exactly the side-effect and auth facts an agent needs before invoking a destructive, open-world call.

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?

Front-loaded with the action, then organized into short labeled lines for operation, scopes, idempotency, destructiveness, and workspace override. The "Luca operation" and scope lines are somewhat boilerplate but each carries a distinct fact.

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

Completeness5/5

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

With annotations and an output schema already present, the description fills the remaining gaps: side-effect confirmation, idempotency behavior, auth/scope requirements, and workspace scoping. Nothing an agent needs to invoke this correctly is missing.

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 80%, so the baseline is 3. The description adds useful meaning for idempotencyKey, confirm, and the workspaceId/workspaceSlug override, but says nothing about the body payload or the event `type` enum, which is the tool's most consequential argument and is left entirely to the schema.

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 and resource: "Queue a canonical test webhook event", which is clearly distinct from the sibling write tools (subscriptions_create/update, events_replay, deliveries_replay). It does not explicitly name which sibling to use instead for real deliveries or replays, so it stops short of a 5.

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 "test" framing makes the intended context (verifying an endpoint/subscription) clear, and it lists the operational preconditions: webhooks:write scope, Idempotency-Key, and confirm: true. It gives no explicit when-not-to-use guidance or pointer to the alternative tool for triggering real or replayed events.

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