Skip to main content
Glama

HonestCRM

Create a deal

create_deal

Create a deal in a pipeline 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": {
      "title": "<title>"
    },
    "name": "create_deal"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesDeal 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.
tagIdsNoIds of tags to attach (at most 20).
stageIdNoThe open stage to start in. Default: the first open stage. Use list_pipelines to find it.
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).
pipelineIdNoThe pipeline. Default: the first pipeline. Use list_pipelines to find it.
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

C2.8/5.0
Behavior2/5

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

Annotations already disclose that this is a non-readonly, non-idempotent, non-destructive write with no external side effects. The description adds almost nothing beyond restating the purpose; it omits defaults, required relationships such as title, and what happens when optional pipeline or stage values are absent.

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?

The description is a single front-loaded sentence with no filler, but its brevity leaves the tool under-specified for a 14-parameter create operation. It is concise without being sufficiently informative.

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

Completeness2/5

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

Given a creation tool with 14 parameters and multiple relationship/defaulted fields, the description is far too thin. Although the schema and annotations carry much of the burden, the definition should at least clarify required fields and defaulting behavior to be complete.

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 every parameter is already documented in detail, including defaults and enum behavior. The description contributes no additional parameter meaning beyond the schema baseline.

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 a specific verb and resource: "Create a deal," with the additional scope "in a pipeline stage." This clearly distinguishes it from update_deal, move_deal_stage, or list_deals, though it does not name any 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 Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives such as update_deal or move_deal_stage, nor are prerequisites or conditions described. Usage is only implied by the word "Create."

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