Skip to main content
Glama

Create a deal

dosai_create_deal

A deal by hand: the client is found by phone or created. If this client already has an open deal in the pipeline, that one is returned (existing=true) instead of a second. Personal contact: owner/admin only (403). Needs an open stage (not won/lost). Editor or above.

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": {
      "workspace_id": "<workspace_id>",
      "stage_id": "<stage_id>"
    },
    "name": "dosai_create_deal"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
phoneNoWith country code, e.g. 77071234567. Name or phone is required.
titleNoWhat the client buys.
amountNo
currencyNo
stage_idYesStage id, as returned by dosai_list_pipelines.
project_idNoWhich bot (assistant) of the CRM project the deal belongs to; default the first one.
workspace_idYesCRM project (workspace) id, as returned by dosai_list_workspaces.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. Changed3 schema fields 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)$"
    • removedInput schema / properties / stage_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)$"
    • removedInput schema / properties / workspace_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.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false/openWorldHint=false/destructiveHint=false, so the description carries the real burden and does so well: it discloses the existing-deal short-circuit with the existing=true flag, the 403 owner/admin restriction, the requirement for an open (non won/lost) stage, and the editor-or-above role. The cryptic fragment 'Personal contact: owner/admin only (403)' is ambiguous about which field triggers that rule.

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

Conciseness3/5

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

It is short with no filler, but the telegraphic fragment style ('A deal by hand:', 'Personal contact: owner/admin only (403)') sacrifices readability, and the most distinctive behavior – the dedupe return – is buried mid-paragraph.

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 an 8-parameter create mutation with no output schema, the definition covers the key behavioral risks: duplicate suppression, permission failures, and stage validity. It omits default behavior for optional fields like currency/amount and does not describe the returned object beyond existing=true, but the essentials are present.

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 63%, and the description adds meaning mainly for phone (client lookup-or-create is keyed on it) and stage_id (must be an open stage). Currency, amount, project_id, and workspace_id get no treatment in the description, so it only partially compensates for the coverage gap.

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 opening 'A deal by hand' plus the following sentences make clear this is a manual deal creation that finds-or-creates the client and de-duplicates open deals. The verb is implicit rather than stated ('create' comes from the name/title), and it never contrasts itself with siblings like dosai_create_lead, but the resource and scope are unmistakable.

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?

'By hand' implies manual entry and the stage/permission constraints hint at preconditions, but there is no explicit when-to-use versus dosai_create_lead or dosai_update_deal, and no statement of when-not to call it. Usage is inferable rather than guided.

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