Skip to main content
Glama

Connect amoCRM, Bitrix24 or U-ON

dosai_connect_crm
Destructive

Check and connect the owner's CRM in one step, so the bot's leads land there as deals. amocrm: address like company.amocrm.ru and a long-lived token from the integration the owner creates in amoCRM. bitrix24: the incoming webhook address from Bitrix24 (it holds the key, pass it as address). uon: the U-ON account address and API key. Returns the CRM's funnels and stages (metadata) for dosai_update_crm_integration and dosai_set_crm_stage_mapping: keep them, this is the only place they come from. Connecting ANOTHER account or CRM type erases the field and stage mapping of the previous one, so call it once and do not repeat it just to re-read the funnels. Two steps. The key passes through this chat, warn the owner. Requires editor role.

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": {
      "project_id": "<project_id>",
      "crm_type": "<crm_type>",
      "address": "<address>"
    },
    "name": "dosai_connect_crm"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYes
api_keyNo
crm_typeYes
project_idYesFrom dosai_list_projects.
confirm_tokenNoLeave empty on the first call: it changes nothing and returns what will happen and a code. Ask the owner; only after their explicit "yes" call again with the same arguments and this code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project id, as returned by dosai_list_projects."New value: +"From dosai_list_projects."
  2. Changed1 schema field changed
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, and the description adds the concrete consequence the annotation cannot express: connecting another account or CRM erases the previous field and stage mapping. It also discloses the security-relevant behavior that the key transits the chat and the owner should be warned, plus the role requirement and the two-step confirmation flow.

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?

The opening sentence leads with purpose and the credential details follow compactly. Some phrasing is telegraphic ("Two steps.", "keep them, this is the only place they come from"), which costs a little readability but no sentence is filler.

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 destructive, multi-CRM mutation with no output schema, the description covers return values (funnels and stages metadata), side effects on prior mappings, auth/role requirements, and the confirmation protocol. Nothing an agent needs to call it safely is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 40%, but the description compensates substantially: it explains what `address` means per crm_type (amoCRM domain, Bitrix24 webhook that embeds the key, U-ON account address) and what `api_key` is (a long-lived token from a self-created integration). It does not restate the confirm_token semantics in prose, though the schema already documents that parameter well.

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 ("Check and connect the owner's CRM") plus the outcome ("the bot's leads land there as deals"), and enumerates the three supported CRM types with their credential shapes. This is clearly distinguished from siblings like dosai_get_crm_integration and dosai_update_crm_integration, which are named.

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?

Gives explicit when-not guidance ("call it once and do not repeat it just to re-read the funnels"), a prerequisite ("Requires editor role"), a procedural constraint ("Two steps"), and names the downstream tools that consume its output (dosai_update_crm_integration, dosai_set_crm_stage_mapping). The agent knows both when to call it and when not to.

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