Skip to main content
Glama

Новый вебхук

create_quiz_webhook

Добавляет вебхук к опросу. Создаётся выключенным: сначала проверьте отправкой, потом включите через toggle_quiz_webhook — так же устроено в интерфейсе. Адрес должен быть публичным http или https, внутренние адреса не принимаются.

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>",
      "title": "<title>",
      "url": "<url>",
      "method": "<method>"
    },
    "name": "create_quiz_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesАдрес, куда уходят данные. Только публичный http или https.
bodyNoКакие поля ответа слать: список id вопросов (uuid из get_quiz_structure) и имён скрытых переменных.
hoursNoЗадержка перед отправкой в часах: 0, 1, 6, 12 или 24. Ноль — сразу.
titleYesНазвание вебхука, до 255 символов.
methodYesHTTP-метод: get, post, put или patch.
headersNoДополнительные заголовки запроса, список из {"name": "...", "value": "..."}.
quiz_idYesID опроса.
incompleteNoСлать и незавершённые ответы.
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

A4.3/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false), the description discloses the crucial state behavior that the created webhook starts disabled and must be enabled separately, plus an input constraint that internal/private addresses are rejected. This is exactly the kind of side-effect and validation context annotations cannot convey.

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: purpose first, then the disabled-by-default workflow, then the URL constraint. Every sentence carries information the agent needs and there is no 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 a 9-parameter, nested-object mutation with no output schema, the description covers the essential lifecycle (created disabled → test → toggle) and the URL validation rule. It does not say what is returned (notably whether the new webhook's id comes back, which the agent needs for toggle_quiz_webhook) or whether permissions/scopes are required, leaving a small but real gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds a rule the schema does not state: the URL must be public http/https and internal addresses are refused, which materially affects how an agent fills the required url field. Other parameters (body, hours, headers, body_naming) are left entirely to the schema.

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 opens with a specific verb and resource ('Добавляет вебхук к опросу'), making the create operation unmistakable, and it references toggle_quiz_webhook as the follow-up step, which separates it from the update/toggle siblings. It stops short of explicitly contrasting with update_quiz_webhook, so an agent still infers that boundary.

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 workflow: create (arrives disabled), send a test, then enable via toggle_quiz_webhook — mirroring the UI. That tells the agent when this tool is the right entry point and what must follow it. There is no explicit statement of when not to use it (e.g. preferring update_quiz_webhook for existing webhooks).

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