Skip to main content
Glama
Sign In
delega-mcp

delega-mcp

by delega-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

create_webhook

Create a webhook to receive POST notifications for task lifecycle events: created, updated, completed, deleted, assigned, delegated, commented, claimed, released, state_changed, linked.

Instructions

Create a webhook to receive event notifications (admin only). Events: task.created, task.updated, task.completed, task.deleted, task.assigned, task.delegated, task.commented, task.claimed, task.released, task.state_changed, task.linked

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

Input Schema

NameRequiredDescriptionDefault
urlYesHTTPS URL to receive webhook POST requests
eventsYesEvents to subscribe to

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.18.2
  2. Removedv1.13.1
  3. Changed1 schema field changedv1.9.0
    • changedInput schema / properties / events / items / enum
      Previous value: -[
-  "task.created",
-  "task.updated",
-  "task.completed",
-  "task.deleted",
-  "task.assigned",
-  "task.commented"
-]New value: +[
+  "task.created",
+  "task.updated",
+  "task.completed",
+  "task.deleted",
+  "task.assigned",
+  "task.delegated",
+  "task.commented",
+  "task.claimed",
+  "task.released",
+  "task.state_changed",
+  "task.linked"
+]
  4. Addedv1.2.1

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided, so description bears full responsibility. It states admin requirement and events but omits details like idempotency, activation behavior, or security considerations. Minimal disclosure.

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?

Short, front-loaded with verb and resource. Events list is lengthy but informative. Could omit events since they are in schema, but overall efficient.

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?

Adequate for a simple creation tool with 2 parameters and no output schema. Lacks info on return values or side effects, but context signals (100% coverage) compensate partially.

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 covers 100% of parameters with descriptions. The description redundantly lists events that are already in the enum. Adds no new semantic value beyond schema.

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?

Clearly states the action (create) and resource (webhook), with specific context 'admin only' and listing events. Distinguishes from sibling tools like list_webhooks and delete_webhook.

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?

Specifies 'admin only', indicating restricted usage. Does not explicitly state when to use vs. alternatives, but the event list clarifies subscribing scenarios.

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