Skip to main content
Glama

Правка вебхука

update_quiz_webhook
Destructive

Изменяет вебхук опроса. Не переданные поля сохраняют текущие значения, поэтому можно слать только то, что меняется. Идентификатор вебхука — из get_quiz_webhooks.

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": {
      "quiz_id": "<quiz_id>",
      "webhook_id": "<webhook_id>"
    },
    "name": "update_quiz_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoАдрес, куда уходят данные. Только публичный http или https.
bodyNoКакие поля ответа слать: список id вопросов (uuid из get_quiz_structure) и имён скрытых переменных.
hoursNoЗадержка перед отправкой в часах: 0, 1, 6, 12 или 24.
titleNoНазвание вебхука, до 255 символов.
methodNoHTTP-метод: get, post, put или patch.
headersNoДополнительные заголовки запроса, список из {"name": "...", "value": "..."}.
quiz_idYesID опроса.
is_activeNoВключён ли вебхук.
incompleteNoСлать и незавершённые ответы.
webhook_idYesID вебхука (из get_quiz_webhooks).
body_namingNoПереименование полей: объект «id поля → свой ключ» для полей из body.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / body / description
      Previous value: -"Шаблон отправляемых данных: какие поля ответа слать."New value: +"Какие поля ответа слать: список id вопросов (uuid из get_quiz_structure) и имён скрытых переменных."
    • addedInput schema / properties / body / items
      Added value: +{
      +  "type": "string"
      +}
    • changedInput schema / properties / body / type
      Previous value: -"object"New value: +"array"
    • changedInput schema / properties / body_naming / description
      Previous value: -"Переименование полей: свой ключ для каждого поля отправки."New value: +"Переименование полей: объект «id поля → свой ключ» для полей из body."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare a non-read-only, destructive, non-idempotent, open-world mutation, so the safety profile is covered. The description adds something the annotations cannot: unpassed fields keep their current values, meaning a partial payload will not wipe the rest of the configuration. It does not warn about consequences of changing url/headers on live delivery, but the key patch semantic is disclosed.

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?

Three short sentences with the mutation and patch semantics front-loaded, followed by the ID provenance hint. Nothing is repeated from the schema and no sentence is filler.

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

Completeness4/5

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

For an 11-parameter mutation with a nested body_naming object and no output schema, the description supplies the two things the schema cannot: partial-update behavior and where webhook_id originates. It lacks any note on side effects of an active webhook being reconfigured, which is the remaining gap.

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% (url, body, hours, method, headers, is_active, incomplete, body_naming all documented with enums and formats), so the baseline is 3. The description only reinforces the webhook_id source already noted in the schema and adds no extra meaning for the nested body_naming or headers parameters.

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 concrete verb plus resource ("Изменяет вебхук опроса" / modifies the quiz webhook) and its name distinguishes it from create_/delete_/get_quiz_webhook siblings. It does not explicitly differentiate from toggle_quiz_webhook, which overlaps via the is_active parameter, so it stops short of a 5.

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?

It states patch-style usage clearly ("можно слать только то, что меняется") and tells the agent where webhook_id comes from (get_quiz_webhooks). It gives no guidance on when to prefer toggle_quiz_webhook for simple on/off changes, nor any exclusions or prerequisites, so usage is implied rather than fully routed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources