Skip to main content
Glama

Досылка в мессенджер

resend_integration_logs

Дослать в мессенджер то, что не ушло. Нужен, когда причина сбоя устранена: бота вернули в группу, токен перевыпустили — накопившиеся заявки иначе так и останутся в журнале. Можно повторить одну запись по log_id или все неудачные за период. Отправка идёт очередью, поэтому в ответе — сколько поставлено в очередь; дошло или нет, покажет get_integration_logs.

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

Input Schema

NameRequiredDescriptionDefault
log_idNoID одной записи из get_integration_logs. Без него повторяются все неудачные.
date_toNoКонец периода для повтора пачкой, в формате ГГГГ-ММ-ДД.
quiz_idYesID опроса.
date_fromNoНачало периода для повтора пачкой, в формате ГГГГ-ММ-ДД.
integrationYesКуда досылать: telegram или max.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the mutation profile is known. The description adds materially useful behavior beyond that: sending is queued, the response only reports how many were enqueued, and actual delivery must be verified via get_integration_logs. It stops short of warning about duplicate sends when retrying non-idempotent records.

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?

Four short sentences ordered as purpose → when to use → how to scope → what the response means, with the trigger condition front-loaded right after the purpose. No filler or repeated structured data beyond what is needed to tie the sentences together.

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

Completeness5/5

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

For a five-parameter mutation tool with no output schema, the description covers the missing return-value semantics (a queue count, not a delivery result) and names the verification tool. Nothing an agent needs in order to invoke it correctly or interpret its response is absent.

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%, so all five parameters, including the log_id-vs-period precedence and the telegram/max enum, are already documented in the schema. The description's sentence about retrying one record by log_id or all failures for a period restates rather than extends that information, 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 (записи, не ушедшие в мессенджер), and scopes it to the integration log rather than generic messaging. The final clause explicitly routes the agent to sibling get_integration_logs for delivery confirmation, so the tool is distinguishable from it without opening either schema.

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 a concrete trigger condition — the failure cause has been fixed (bot re-added to the group, token reissued) — and explains the two operating modes, single record by log_id or all failures in a period. It does not explicitly exclude the sibling resend tools for email/webhook channels, leaving channel choice to be inferred.

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