Skip to main content
Glama

Журнал доставки вебхука

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

Input Schema

NameRequiredDescriptionDefault
pageNoНомер страницы, по умолчанию 1.
statusNoТолько записи с этим статусом: sent — дошли, failed — не дошли, queued — ждут отправки. Без него — все записи. meta.counts всегда по всему журналу.
quiz_idYesID опроса.
per_pageNoЗаписей на странице, по умолчанию 20, максимум 30.
webhook_idYesID вебхука (из get_quiz_webhooks).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / status
      Added value: +{
      +  "description": "Только записи с этим статусом: sent — дошли, failed — не дошли, queued — ждут отправки. Без него — все записи. meta.counts всегда по всему журналу.",
      +  "enum": [
      +    "sent",
      +    "failed",
      +    "queued"
      +  ],
      +  "type": "string"
      +}
  2. 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=true, idempotentHint=true and destructiveHint=false, so safety is covered. The description adds value beyond that by disclosing what the records contain (delivery success plus the receiver's status code and body) and framing the tool as the sole diagnostic path, which fills the gap left by the absent output 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 sentences, both front-loaded: the return content comes first, then the diagnostic rationale. No filler, no restatement of the title, and nothing that duplicates structured fields.

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 read-only log tool with no output schema, the description tells the agent what a record contains and when the tool is the right diagnostic. Minor omissions such as pagination size limits and the aggregate meta.counts are covered only by the schema, not the description.

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%, with page, per_page, status and webhook_id all documented in the schema itself, including defaults and the max of 30. The description adds no parameter-level meaning beyond that, so it sits at the baseline where the schema does the work.

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 first sentence names a specific verb and resource ('Возвращает журнал отправок вебхука') and enumerates the payload the agent gets back (delivery outcome, response code, response body). The second sentence separates it from the webhook configuration tool by stating that the config doesn't reveal this, so an agent can distinguish it from get_quiz_webhooks.

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?

The description gives a clear use case — diagnosing 'why data isn't arriving' — and implicitly positions the webhook settings tool as insufficient for that question. It does not name an explicit exclusion or a sibling alternative for other log types (e.g. get_integration_logs), so guidance is strong but not exhaustive.

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