Skip to main content
Glama
Sign In

HotCodePush

by com.hotcodepush
OverviewDiscussionsAdmin

Test a webhook

test_webhook

Send one sample event, webhook.test, to a webhook's URL through the normal delivery path, and answer the receiver's response. Use this right after create_webhook or a URL change to check the receiver accepts the payload; a disabled webhook is tested all the same, and the outcome never counts toward the failures that disable it. Returns the settled delivery with status, responseCode and the first 4 KB of responseBody. Do not use this to send a real event again: use redeliver_webhook_delivery.

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": {
      "organizationId": "<organizationId>",
      "webhookId": "<webhookId>"
    },
    "name": "test_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
webhookIdYesThe id of the webhook, e.g. "a1b2c3d4-0000-4000-8000-000000000000". Use `list_webhooks` to look it up by name.
organizationIdYesThe id of the organization, e.g. "a1b2c3d4-0000-4000-8000-000000000000". Use `list_organizations` to look it up.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false, destructiveHint=false and openWorldHint=true. The description adds real behavioral context beyond that: disabled webhooks are still tested, the outcome never counts toward the failures that disable a webhook, and the return includes `status`, `responseCode` and the first 4 KB of `responseBody`.

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?

Three sentences, front-loaded with what the tool does, then when to use it, then what it returns and what not to use it for. Every clause carries information, including the non-obvious disabled-webhook caveat.

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?

There is no output schema, and the description compensates by describing the settled delivery and its fields. Combined with the 100% schema coverage on the two parameters, an agent has everything needed to call this correctly.

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 `webhookId` and `organizationId` are already documented with lookup hints (`list_webhooks`, `list_organizations`). The description adds nothing further about parameters, so the baseline 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 (send one sample event) plus the exact event name `webhook.test` and the path it takes (the normal delivery path). It distinguishes itself from siblings like `redeliver_webhook_delivery` by naming that tool explicitly.

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

Usage Guidelines5/5

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

Gives a concrete trigger ('right after `create_webhook` or a URL change to check the receiver accepts the payload') and an explicit exclusion ('Do not use this to send a real event again: use `redeliver_webhook_delivery`'). Both when-to-use and when-not-to-use are covered with the named alternative.

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

All HotCodePush toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources