Skip to main content
Glama
gwmage

Rootr MCP Server

Create, update, or delete a deal in a Rootr CRM

rootr_crm_upsert_deal

Create, update, or delete CRM deals. Manage deal details including status, value, contacts, and pipeline.

Instructions

Create a new deal (omit dealId; defaults to the CRM's first pipeline if pipelineId is omitted), update an existing one (pass dealId + fields to change — set status to "won" or "lost" to close it, with wonLostReason, or "open" to reopen), or delete one (pass dealId and delete: true). To MOVE a deal between kanban stages, prefer rootr_crm_move_deal instead of patching stageId here. Part of a Rootr (루터) CRM node: a full sales CRM (companies, contacts with lifecycle stages + auto lead-scoring, multi-pipeline deals/kanban, activity timeline, follow-up tasks), auto-linked into the knowledge graph.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoDeal name (required when creating)
tagsNo
crmIdYesCRM node id
valueNoDeal value
customNoCustom field values, keyed by field id/name
dealIdNoExisting deal id to update/delete; omit to create a new deal
deleteNoIf true (with dealId), delete the deal instead of updating
sourceNoAcquisition source
statusNoopen | won | lost (patch only)
ownerIdNoOwning user id
stageIdNoStage id (see rootr_crm_move_deal to change stage on an existing deal)
contactsNoAdditional contacts on the deal with an optional role, e.g. "champion" | "economic buyer"
currencyNoCurrency code, e.g. "USD" | "KRW"
priorityNolow | medium | high
companyIdNoAssociated company id
pipelineIdNoPipeline id; defaults to the CRM's first pipeline when creating
probabilityNoWin probability override 0-100
wonLostReasonNoReason text when closing status to won/lost
primaryContactIdNoPrimary contact id
expectedCloseDateNoISO date string
Behavior1/5

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

The description discloses deletion capability, but annotations set destructiveHint: false, creating a contradiction. According to rules, score 1 when contradiction exists.

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?

Description is front-loaded with core functionality but includes a lengthy paragraph about the CRM node that is extraneous for tool invocation.

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?

No output schema exists, but description does not clarify return values. However, it covers input semantics well for a complex tool.

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 95%, so baseline is 3. Description adds semantics like default pipeline, status semantics, and move guidance, elevating it to 4.

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

Purpose5/5

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

The description clearly states it can create, update, or delete a deal using specific verbs. It distinguishes from sibling tool rootr_crm_move_deal by advising against using it for moving stages.

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

Usage Guidelines5/5

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

Explicitly explains when to use which operation: omit dealId to create, pass dealId to update/delete, use delete:true to delete. Also provides guidance on status changes and warns against using stageId for moves.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gwmage/rootr-cli'

If you have feedback or need assistance with the MCP directory API, please join our Discord server