Skip to main content
Glama

Состояние интеграций опроса

get_quiz_integrations
Read-onlyIdempotent

Показывает, куда опрос отправляет ответы кроме почты: Telegram, MAX, AmoCRM, Битрикс24, Zapier, Google Таблицы. По каждой видно, подключена ли она, включена ли отправка и разрешает ли её тариф. Отвечает на «почему заявки не приходят в CRM». Только чтение: подключение — это вход в чужой аккаунт или ввод токена. Вебхуки живут отдельными инструментами, начните с get_quiz_webhooks.

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

Input Schema

NameRequiredDescriptionDefault
quiz_idYesID опроса.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is known; the description nonetheless explains why it is read-only (connecting needs an account login or token) and what each row reports (connected, sending enabled, plan allowance). What it doesn't cover — any auth or rate-limit behavior of the call itself — is minor here, so it adds real value beyond the annotations without being exhaustive.

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?

Every sentence earns its place: the destination list, the per-integration fields, the diagnostic question the tool answers, the read-only rationale, and the pointer to get_quiz_webhooks. The most important framing (what it shows) comes first, with routing guidance last.

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?

With no output schema, the description carries the burden of describing returns and does so — it names the per-integration statuses the caller will see. For a one-parameter read tool with full annotation coverage, nothing an agent needs in order to call it correctly or interpret it is missing.

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?

There is a single required parameter and schema description coverage is 100%, so the schema already documents quiz_id as "ID опроса". The description adds no further semantics about the identifier (format, source, or how to obtain it), which is acceptable at this coverage but puts it at the baseline.

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 gives a specific verb and resource ("Показывает, куда опрос отправляет ответы") and enumerates every destination it covers: Telegram, MAX, AmoCRM, Битрикс24, Zapier, Google Таблицы. It also names the sibling it is not — "Вебхуки живут отдельными инструментами" — so an agent can route between get_quiz_integrations and get_quiz_webhooks 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is stated explicitly: use it to answer "почему заявки не приходят в CRM". The boundary against alternatives is explicit in both directions — webhooks are handled elsewhere, and connecting an integration is out of scope because it requires "вход в чужой аккаунт или ввод токена". This leaves nothing to inference.

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