Skip to main content
Glama

Поля CRM и текущее сопоставление

get_quiz_crm_fields
Read-onlyIdempotent

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

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

Input Schema

NameRequiredDescriptionDefault
crmYesКакая CRM: amocrm или bitrix24.
quiz_idYesID опроса.
sectionsNoКакие справочники нужны: lead, deal, contact, company, users, pipelines, types. По умолчанию lead и contact — каждый справочник это отдельный запрос в CRM.
deal_category_idNoНомер воронки сделки: стадии принадлежат воронке, и без него портал отдаёт стадии воронки по умолчанию. Только для Bitrix24.

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=true and destructiveHint=false, but the description adds non-obvious behavior: the catalogs are fetched via live CRM requests, so the call is slow and will fail if portal access has been revoked. It also notes the response carries a mapping_tool field. It stops short of describing result size, partial-failure behavior, or pagination of large directories.

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?

It is a single dense paragraph that front-loads what is returned, then the read-only constraint and alternatives, then the latency/failure caveat. Every clause carries information, though the run-on structure and duplicated emphasis on 'только читает' cost a little crispness.

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 and four parameters, the description does the heavy lifting: it says what comes back (reference catalogs plus saved mapping), how it is obtained (live CRM calls), and what can go wrong (revoked portal access). Missing only details on result volume and per-section failure semantics for a tool that fans out into multiple CRM requests.

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%, so the schema already documents crm, quiz_id, sections and deal_category_id, including the note that each section is a separate CRM request and that deal_category_id is Bitrix24-only. The description only loosely restates the catalog list ('воронки со стадиями') without adding syntax or defaults beyond the schema, so the 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 first sentence names a concrete resource (CRM reference data plus the currently saved field mapping) and states what it contains: which entities go to amoCRM/Bitrix24 and into which fields. It enumerates the returned catalogs (lead, deal, contact, company, pipelines with stages, users, types) and is clearly distinguishable from the mapping-editing siblings.

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?

It explicitly separates read from write: 'Сам инструмент только читает; править сопоставление — manage_quiz_crm_mapping (Bitrix24) и manage_quiz_amocrm_mapping (amoCRM)', and even points to the mapping_tool field in the response for discovering the right editor. That is a direct when-to-use/when-not-to-use routing rule with named alternatives.

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