Skip to main content
Glama

subscribe

Register a webhook to receive a push notification when a trigger fires and return a subscription ID for tracking.

Instructions

Register a webhook to be woken (pushed) when a trigger fires. Returns a subscription id.

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": {
      "trigger": "<trigger>",
      "url": "<url>"
    },
    "name": "subscribe"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
triggerYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses only that this is a push/webhook registration and that an id is returned; it says nothing about required permissions, duplicate-URL behavior or idempotency, URL validation, retry semantics, or how a subscription is later removed.

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?

Two short sentences, front-loaded with the core action and mechanism, with no filler. The return-value note is arguably redundant with the output schema but costs little.

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-parameter tool with an output schema (so return values need not be explained) the description covers the core action. It is nonetheless thin on prerequisites and lifecycle for a tool that creates persistent server-side state.

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 0%, so the description must compensate, and it does partially: 'webhook' clarifies that url is an endpoint to be called, and 'when a trigger fires' clarifies that trigger is the firing event. It still does not say whether trigger is a name, an id, or an expression, nor what URL schemes are accepted.

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 uses a specific verb and resource ('Register a webhook') and states the mechanism ('woken/pushed when a trigger fires'). However, it does not distinguish this tool from plausible siblings such as create_trigger, leaving an agent unsure whether it is creating a trigger or attaching a delivery endpoint to one.

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 explicit when-to-use or when-not-to-use guidance, and no named alternative. The phrase 'when a trigger fires' implies a trigger must already exist, but this prerequisite is left to inference rather than stated.

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