Skip to main content
Glama
Pombus MCP Server

Pombus MCP Server

Official

Create webhook

create_webhook

Registers a webhook on a specified pod to send event notifications to a URL, using a pod ID within the key's permitted scope.

Instructions

Register a webhook on the pod.

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>",
      "url": "<url>"
    },
    "name": "create_webhook"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/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. Beyond that the description adds only the pod scoping phrase; it does not say whether duplicate URLs are rejected, whether the new webhook fires immediately, whether a signing secret is generated, or what failures look like for a non-idempotent open-world mutation.

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

Conciseness3/5

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

It is a single front-loaded sentence with zero padding, which is structurally sound. However, the brevity is under-specification rather than efficiency: the sentence does not carry enough content to be useful, so conciseness is not a virtue here.

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 create-mutation with 3 parameters, partial schema coverage, no output schema and no return-shape information anywhere, the description should cover endpoint requirements, event selection and post-creation behavior. It covers none of these, leaving the agent to guess at call correctness.

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 description coverage is only 33%: pod_id is documented in the schema, but url and events are bare untyped-in-meaning fields. The description does not compensate by explaining that url must be a reachable HTTPS endpoint, or what events accepts and what an empty/omitted events array means (all events vs none). This is a significant gap for a 3-parameter mutation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Register a webhook on the pod" gives a verb and a resource, but it largely restates the tool name and title, adding only the pod scoping hint. It says nothing about what a webhook registration entails (target URL, subscribed events), so an agent gets only a minimal restatement rather than a differentiating description.

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 at all: no mention of when to create a new webhook versus update_webhook for an existing one, no prerequisite that the pod must already exist, and no note on what happens if a webhook for that URL is already registered. The agent must infer routing from the sibling names alone.

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