Skip to main content
Glama

Досылка вебхука

resend_quiz_webhook_log

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

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": "resend_quiz_webhook_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
log_idNoID записи журнала (из get_quiz_webhook_logs).
date_toNoКонец периода для массовой додосылки, в формате ГГГГ-ММ-ДД.
quiz_idYesID опроса.
date_fromNoНачало периода для массовой додосылки, в формате ГГГГ-ММ-ДД.
webhook_idYesID вебхука (из get_quiz_webhooks).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so safety and repeatability are covered structurally. The description adds a genuinely useful behavioral fact — that delivery is replayed from stored data without requiring a new respondent submission — but says nothing about what happens on duplicate delivery to the external receiver, permission requirements, or bulk-mode side effects, which matters for an openWorld operation.

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?

A single short sentence, front-loaded with the action and followed by the operational trigger; nothing is padded or repeated from the schema. No restructuring would improve it without adding information.

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

Completeness3/5

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

For a five-parameter tool with two distinct modes (single log replay versus date-range mass resend) and external side effects, the description only covers the single-entry case, leaving the bulk path and the relationship between log_id and the required quiz_id/webhook_id to the schema. Because the schema is fully documented this is survivable, but the description is not complete on its own.

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%, including the log_id, quiz_id and webhook_id sources and the ГГГГ-ММ-ДД format, so the baseline is 3. The description adds no parameter-level meaning and, by framing the tool solely as "по записи журнала", it does nothing to explain the periodic bulk path (date_from/date_to) or that log_id is optional while quiz_id and webhook_id are required.

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 and resource: it repeats the delivery for a journal entry ("Повторяет отправку по записи журнала"), which is distinguishable from the read-oriented sibling get_quiz_webhook_logs and from resend_quiz_email_log by the webhook payload. However, it never names a sibling alternative or clarifies that the tool also supports a bulk date-range mode, so differentiation is implicit.

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 clear use context — after the receiver is fixed, without waiting for a new respondent response — which tells an agent exactly when this tool is preferable to waiting for fresh traffic. There are no explicit exclusions or mention of the alternative bulk mode (date_from/date_to) or the sibling tools that produce the log IDs, so guidance is clear but not complete.

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