Skip to main content
Glama

Отправка ответов в CRM

manage_quiz_crm
Destructive

Отправка ответов в CRM — amoCRM или Bitrix24. Показывает, включена ли отправка, включает и выключает её и проверяет, живо ли подключение: токен отзывают на стороне CRM, и со стороны опроса это выглядит как молчащая интеграция. Сопоставление полей опроса с полями лида, сделки и контакта — отдельными инструментами: справочники и текущее сопоставление в get_quiz_crm_fields, правка — manage_quiz_crm_mapping (Bitrix24) и manage_quiz_amocrm_mapping (amoCRM). Подключение портала делают в кабинете: там вход в аккаунт CRM. Состояние всех интеграций опроса — в get_quiz_integrations.

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>",
      "crm": "<crm>",
      "action": "<action>"
    },
    "name": "manage_quiz_crm"
  }
}

Input Schema

NameRequiredDescriptionDefault
crmYesКакая CRM: amocrm или bitrix24.
actionYesЧто сделать: show — состояние, activate — включить отправку, deactivate — выключить, check — проверить связь с CRM.
quiz_idYesID опроса.

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 destructiveHint=true, openWorldHint=true and idempotentHint=false, so the safety bar is partially covered. The description adds genuinely new behavioral context — that tokens can be revoked on the CRM side and that this manifests as a 'silent' integration, which explains why 'check' exists — plus the dashboard-login prerequisite. It does not say what deactivation actually destroys or whether disabling is reversible, which leaves a gap for a destructive-flagged mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Capability statement is front-loaded in the first sentence, followed by routing information and the auth precondition. The token-revocation aside is useful but slightly digressive, and the middle sentence packs two sibling tools plus their scope into one dense clause. Nothing is plainly redundant, though some tightening would help.

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 3-parameter toggle/check tool with no output schema, the description covers purpose, routing to siblings, and the portal-login requirement well. The remaining gap is what each action returns or changes — especially whether deactivate stops future sends only or discards configuration — which matters given the destructive hint and the absent output schema.

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% and both enums are documented inline, so the schema already carries the parameter meaning. The description's phrasing ('показывает, включает и выключает', 'проверяет, живо ли подключение') loosely mirrors the show/activate/deactivate/check actions and adds nuance only for 'check'. Baseline 3 is appropriate when the schema does the heavy lifting.

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 opens with a concrete verb+resource ('Отправка ответов в CRM — amoCRM или Bitrix24') and then enumerates the four capabilities: showing enablement state, enabling, disabling, and checking connection liveness. It explicitly separates itself from the field-mapping siblings and from the aggregate integrations tool, so an agent can distinguish it without opening any 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?

Alternatives are named with their roles: get_quiz_crm_fields for dictionaries/current mapping, manage_quiz_crm_mapping for Bitrix24 edits, manage_quiz_amocrm_mapping for amoCRM edits, and get_quiz_integrations for overall survey integration state. It also states that portal connection must happen in the dashboard, which is an explicit precondition rather than something 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