Skip to main content
Glama

Журнал отправок мессенджера

get_integration_logs
Read-onlyIdempotent

Показывает журнал отправки ответов в мессенджер — Telegram или MAX. Это ответ на «заявки не приходят в Telegram»: в журнале виден текст отказа (бота выгнали из группы, чат удалён, токен отозван) и число неотправленных. Журнал вебхуков — отдельный инструмент get_quiz_webhook_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": "get_integration_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoСтраница журнала, с 1. Записи идут от новых к старым.
statusNoТолько записи с этим статусом: sent — дошли, failed — не дошли, queued — ждут отправки. Без него — все записи. Поле counts всегда по всему журналу.
quiz_idYesID опроса.
per_pageNoСколько записей на странице, от 1 до 200. По умолчанию 20.
integrationYesКакой журнал: telegram или max.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / status
      Added value: +{
      +  "description": "Только записи с этим статусом: sent — дошли, failed — не дошли, queued — ждут отправки. Без него — все записи. Поле 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, idempotentHint and destructiveHint=false, so safety is covered. The description adds real behavioral value by describing what the log actually contains — refusal reason text (bot removed, chat deleted, revoked token) and the unsent count — which tells the agent what evidence it will get back.

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 compact sentences with zero filler: resource first, diagnostic payoff second, sibling disambiguation last. Front-loaded and every sentence earns its place.

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 compensates by sketching the log's contents, and read-only annotations cover safety. Only minor gaps remain, such as ordering/pagination behavior, which the schema already handles adequately.

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 coverage is 100%, and the schema itself documents page, per_page, status enums and the counts-per-whole-log caveat. The description only echoes the telegram/max choice already captured by the integration enum, so it adds little beyond structured data — baseline 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?

The description names a specific verb and resource ('Показывает журнал отправки ответов в мессенджер — Telegram или MAX') and explicitly separates itself from the webhook log by naming get_quiz_webhook_logs. An agent can distinguish it from the sibling 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?

It gives a concrete diagnostic scenario ('заявки не приходят в Telegram') that tells the agent exactly when to reach for this tool, and it redirects webhook-log questions to get_quiz_webhook_logs. It does not state an explicit exclusion for the resend variant, but the primary use context is clear.

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