Skip to main content
Glama

Change a deal

dosai_update_deal
Destructive

What the client buys (title) and the amount of a deal. Only what you pass changes. 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>",
      "deal_id": "<deal_id>"
    },
    "name": "dosai_update_deal"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
amountNonull clears the amount.
deal_idYesDeal id, as returned by dosai_list_deals (a deal is a lead of the CRM).
currencyNo
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. Changed2 schema fields changed
    • removedInput schema / properties / deal_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

B3.3/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds two things annotations cannot convey: partial-update semantics ("Only what you pass changes") and an authorization requirement ("Editor or above"). It stops short of explaining why the operation is flagged destructive or whether overwriting title/amount is recoverable, which keeps it below a 5.

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?

Three short clauses with zero filler, and the field/behavior information is front-loaded ahead of the permission note. The telegraphic style (missing verb, parenthetical field mapping) is slightly terse but readable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-parameter mutation with no output schema, the definition covers the essentials: which fields are editable, partial-update behavior, and the role required. Missing is any treatment of the destructiveHint=true reality — nothing says what is lost or whether a bad title/amount overwrite can be undone — and currency selection is left entirely unexplained.

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?

At 60% schema coverage, the baseline is 3, and the description earns its keep by clarifying the otherwise undocumented `title` parameter ("What the client buys"). However, `currency` remains undocumented in both schema and description, and the amount-clearing behavior is already spelled out in the schema, so the net addition beyond structured data is modest.

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

Purpose3/5

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

The description enumerates the mutable fields ("What the client buys (title) and the amount of a deal") but never states a verb — the update action is only inferable from the tool name and title. It does not distinguish this from dosai_update_lead, dosai_move_deal, or dosai_create_deal in the sibling set, so an agent must rely on the name alone to pick it.

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" implies partial-update usage and "Editor or above" gives a permission precondition, which is more than nothing. But there is no explicit when-to-use-vs-alternatives guidance (e.g. versus move_deal for pipeline changes or update_lead for lead fields) and no statement of what cannot be changed here.

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