Skip to main content
Glama

CRM integration settings

dosai_get_crm_integration
Read-onlyIdempotent

How the project works with the connected CRM. what=settings: which funnel, stage and manager a new deal gets, whether the conversation is copied into the deal, whether the bot moves deals between stages, how the bot's fields map to deal fields, and which data the bot actually collects. what=stage_mapping: which CRM stage each step of the bot's funnel corresponds to.

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_get_crm_integration"
  }
}

Input Schema

NameRequiredDescriptionDefault
whatNoDefault settings.
project_idYesFrom dosai_list_projects.

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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so safety is covered. The description adds real substance by enumerating the contents of each mode (deal creation defaults, conversation copying, stage movement, field mapping, collected data), but says nothing about behavior when no CRM is connected or what a failure looks like.

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 `what=...` labeling front-loads the mode split and every clause maps to returned data. It is a long single block of prose rather than separated lines, and the pseudo-key syntax is slightly jargon-heavy, but little is wasted.

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, the description carries the burden of describing returns and does so thoroughly for both modes. The main gap is the absence of any note on prerequisites (e.g., a CRM must be connected) or on what is returned when integration is absent.

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 100%, so the baseline is 3, but the schema's enum description for `what` is nearly useless ('Default settings.'). The description compensates by spelling out precisely what settings vs stage_mapping return, adding genuine meaning beyond the schema.

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?

The description states the resource ('How the project works with the connected CRM') and enumerates the two distinct read modes, so an agent can tell what each returns. It does not, however, contrast itself with nearby siblings such as dosai_get_crm_today or dosai_set_crm_stage_mapping, leaving the boundary implicit.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no alternative is named. The only cue is the implicit read framing plus the two mode descriptions, which an agent must infer means 'call this to inspect CRM configuration.'

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