Skip to main content
Glama

Вебхуки опроса

get_quiz_webhooks
Read-onlyIdempotent

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

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

Input Schema

NameRequiredDescriptionDefault
quiz_idYesID опроса.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds meaning beyond that: it explains that a webhook may have auto-disabled itself after a series of failed sends, which is behavioral context an agent would not get from the annotations or schema.

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 with zero filler: the returned fields come first, then the workflow constraint. Nothing is repeated from the title or the schema, and the imperative rule is front-loaded at the end where it lands.

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?

With no output schema, the description usefully names the returned fields and their meanings, which is exactly the gap it must fill for a single-parameter read tool. Minor omissions remain: nothing about ordering, pagination, or behavior when a quiz has no webhooks.

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?

Only one parameter, quiz_id, and the schema documents it fully at 100% coverage. The description adds no extra semantics about the parameter (such as where the quiz ID is obtained), so the baseline of 3 applies.

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?

States a specific verb and resource (returns a quiz's webhooks) and enumerates what the response contains: address, method, enabled flag, and self-disabled-after-failures state. That field list clearly separates it from the sibling get_quiz_webhook_logs, which returns delivery history rather than configuration state.

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?

Gives an explicit operational rule: webhook IDs come only from this tool, so read the list before any edit. That is clear when-to-use guidance for a prerequisite read step, though it does not name a specific alternative or state a when-not-to-use case.

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