Skip to main content
Glama

Change CRM integration settings

dosai_update_crm_integration
Destructive

Change how leads go to the connected CRM; only what you pass changes. default_pipeline_id, default_stage_id, default_responsible_ids: where a new deal lands and who gets it (ids come from the answer of dosai_connect_crm). mirror_messages: copy the conversation into the deal; mirror_scope all or bot_only. bot_moves_stages: the bot moves the deal as the client progresses. field_mapping: bot field name to CRM field id (replaces the whole mapping). 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>"
    },
    "name": "dosai_update_crm_integration"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesFrom dosai_list_projects.
mirror_scopeNo
field_mappingNo
mirror_messagesNo
bot_moves_stagesNo
default_stage_idNo
default_deal_titleNo
default_pipeline_idNo
default_responsible_idsNo

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

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, and the description adds real context beyond them: field_mapping 'replaces the whole mapping' (the specific destructive behavior), the editor-role requirement, and where the ids originate. It stops short of describing what happens to existing deals or the response, but the key risk is disclosed.

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?

Front-loaded with the core action and the partial-update rule, then a compact per-parameter glossary. The semicolon-chained style is dense but every clause carries information; no filler sentences.

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 9-parameter destructive mutation with a nested object and no output schema, the description covers nearly all parameters plus the role requirement and the replace-semantics risk. The omission of default_deal_title is the only notable gap.

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 description coverage is only 11%, so the description must carry the load, and it largely does: it explains default_pipeline_id/default_stage_id/default_responsible_ids, mirror_messages, mirror_scope, bot_moves_stages, and field_mapping's key/value shape. Only default_deal_title is left undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Change how leads go to the connected CRM', which is clearly distinct from dosai_connect_crm (setup) and dosai_get_crm_integration (read). It does not explicitly name a sibling it is not, but the scope is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

'only what you pass changes' gives a valuable partial-update cue, and 'Requires editor role' states a prerequisite. However, it never says when to prefer this over dosai_set_crm_stage_mapping or dosai_connect_crm, and gives no when-not guidance.

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