Skip to main content
Glama
Sign In
booking_chest

booking_chest

by dsddet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

update_webhook

Update specific fields of a webhook configuration, such as subscriber URL or active status, using a partial PATCH request.

Instructions

Update a webhook (PATCH — partial update).

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": {
      "webhook_id": "<webhook_id>",
      "fields": "<fields>"
    },
    "name": "update_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsYesFields to update (e.g., {"subscriberUrl": "...", "active": false})
webhook_idYesWebhook ID

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It only discloses that the tool performs a partial update (PATCH), but omits critical behavioral traits such as idempotency, required permissions, side effects, or rate limits. For a mutation tool, this is insufficient.

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?

The description is a single sentence that is front-loaded with the key purpose and method. Every word earns its place, and there is no unnecessary information. It is appropriately sized for the tool's simplicity.

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?

Given that the tool has an output schema and only two parameters, the description is minimally complete. However, it lacks guidance on usage context, prerequisites, and behavioral details, which are needed for an agent to confidently select and invoke the tool among many webhook siblings.

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 the baseline is 3. The description does not add any parameter-specific meaning beyond what the schema already provides (e.g., the fields parameter example is in the schema). No additional enrichment is present.

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?

The description clearly states the verb 'Update' and the resource 'a webhook', and specifies 'PATCH — partial update' which distinguishes it from other webhook operations like create_webhook, delete_webhook, or get_webhook. This provides a specific verb+resource+method, making the purpose immediately clear.

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

Usage Guidelines3/5

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

The description implies that this tool is for partial updates via the 'PATCH' mention, but it does not explicitly state when to use it versus alternatives such as create_webhook or delete_webhook. No exclusions or context for when not to use are provided, relying on the agent to infer from the sibling tool names.

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