Skip to main content
Glama
Pombus MCP Server

Pombus MCP Server

Official

Test webhook

test_webhook

Send a test delivery to a webhook in a permitted pod to verify endpoint delivery before relying on it.

Instructions

Send a test delivery to a webhook.

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": {
      "pod_id": "<pod_id>",
      "webhook_id": "<webhook_id>"
    },
    "name": "test_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
pod_idYesA pod id the key can reach. The server rejects any id outside this key's scope.
webhook_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds essentially nothing beyond restating the name: it does not say what payload is delivered, whether the call mutates stored webhook state, whether failures surface as errors or as a delivery result, or whether repeated calls send repeated deliveries (which the non-idempotent hint implies).

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 twelve-word sentence with the action front-loaded and no filler. Its brevity is close to under-specification rather than wasteful verbosity, but as a structural matter nothing needs trimming.

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

Completeness2/5

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

For a two-parameter, non-idempotent, open-world tool with no output schema, the description should explain what a 'test delivery' contains and how the result is reported, since the agent has no return-value documentation to fall back on. Neither is addressed, leaving a real gap for an externally visible side-effecting call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: pod_id is documented in the schema as a scoping constraint, while webhook_id is bare. The description mentions neither parameter and gives no hint that pod_id scopes access or that webhook_id must identify a webhook within that pod, so it fails to compensate for the coverage gap.

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+resource combination ('send a test delivery to a webhook'), which is clear enough to distinguish it from the CRUD siblings named create_webhook, get_webhook, update_webhook and delete_webhook. It stops short of a 5 because it never explicitly names or contrasts itself with any alternative, leaving the differentiation to inference.

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 when-to-use guidance: nothing says to call this after creating a webhook, before enabling it, or only when validating an endpoint. There are also no exclusions or prerequisites (e.g., that the target endpoint must be reachable). The agent must infer all of the context from the tool name.

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