Skip to main content
Glama

HonestCRM

Update a deal

update_deal
DestructiveIdempotent

Change fields of a deal, such as title, value or expected close date. Send only the fields to change. It does not change the stage.

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": {
      "id": "<id>"
    },
    "name": "update_deal"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe id of the deal.
titleNoDeal title.
valueNoDeal value in major units of the workspace currency, such as 18400.5.
customNoCustom field values as an object of custom field id to value.
companyIdNoThe id of the company the deal is with.
productIdNoThe id of the product the deal is about.
valueTypeNoone_time, or monthly (a monthly value counts 12 times in totals).
ownerUserIdNoThe id of the user who owns the deal. Default: the signed-in user.
leadSourceIdNoThe id of the lead source.
productPlanIdNoThe id of a plan of that product. Without a value, the deal takes the plan's price.
primaryContactIdNoThe id of the deal's first contact.
expectedCloseDateNoExpected close date as YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value with partial-update semantics and the stage restriction, but says nothing about what happens to fields not supplied being preserved, permissions requirements, or side effects on related records.

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 sentences, front-loaded with the purpose, followed by the patch semantics and the exclusion. No filler; the only minor weakness is that the exclusion could be tied to a named alternative rather than left as a bare negative.

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 12-parameter mutation with nested custom-field objects and no output schema, the definition covers the essentials: what it changes, how to send partial data, and the one field it cannot touch. An agent could invoke it correctly, though return shape and the null-vs-omit distinction are left to the schema.

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 description coverage is 100%, so all 12 parameters including custom field ids, valueType and productPlanId are already documented in the schema. The description only echoes three field names and adds no syntax, format, or edge-case 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?

States a specific verb and resource ('Change fields of a deal') and names representative fields (title, value, expected close date). It also rules out the stage field, which implicitly separates it from move_deal_stage, but never names that sibling explicitly.

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

Usage Guidelines4/5

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

'Send only the fields to change' tells the agent this is a partial/patch-style update rather than a full replace, and 'It does not change the stage' is an explicit exclusion. What is missing is a pointer to the tool that does change stage (move_deal_stage) or any note about preconditions such as needing an existing deal read first.

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