Skip to main content
Glama

Вебхук вкл и выкл

toggle_quiz_webhook

Включает или выключает вебхук. Выключенный остаётся настроенным, но отправки по нему не идут. После серии неудач вебхук отключается сам — включить обратно можно здесь же, когда приёмник починили.

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>",
      "is_active": "<is_active>"
    },
    "name": "toggle_quiz_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
quiz_idYesID опроса.
is_activeYestrue — включить, false — выключить.
webhook_idYesID вебхука (из get_quiz_webhooks).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations it explains real behavior: a disabled webhook stays configured but stops delivering, and the system self-disables after repeated failures. That is exactly the context the annotations (destructiveHint=false, idempotentHint=false) cannot convey. It still says nothing about permissions or the response, so it is not exhaustive.

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, no redundancy, with the core action front-loaded and the state semantics following. Every sentence carries distinct information.

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 a three-parameter toggle with full schema coverage and annotations, the description covers what changes, what persists, and the recovery path. Only return shape and permission requirements are absent, which is minor here.

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 100% and all three parameters carry their own descriptions, including the is_active true/false meaning and the pointer to get_quiz_webhooks for webhook_id. The prose adds no further parameter detail, so the baseline 3 applies.

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 states a specific verb pair and resource ("Включает или выключает вебхук"), which is unambiguous. It does not explicitly distinguish itself from create_quiz_webhook, update_quiz_webhook or delete_quiz_webhook, so the agent must infer the split from the verb alone.

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?

It gives a concrete situation that selects this tool: a webhook that auto-disabled after a run of failures can be switched back on here once the receiver is fixed. It stops short of naming alternatives (e.g. update_quiz_webhook for changing the URL) or stating when not to use it.

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