Skip to main content
Glama
ptaramona

Conduyt MCP Server

by ptaramona
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

conduyt_create_deal

Create a new deal in a pipeline with attributes like value, currency, priority, close date, and custom fields. Requires a pipeline and stage ID for correct placement.

Instructions

Create a new deal in a pipeline with full attributes. Requires a pipeline and stage ID — use conduyt_list_pipelines to discover them. Supports currency (e.g. GBP), probability, priority, expected close date, and structured custom-field values.

Input Schema

NameRequiredDescriptionDefault
titleYesDeal title (e.g. 'Acme Corp — Enterprise Plan')
valueNoDeal value (numeric, in the deal's currency)
sourceNoAttribution source for THIS deal — the trigger that produced it (e.g. 'sms-reply', 'booking:demo', 'partner-referral'). Each deal carries its own source; the contact's source stays the first-touch acquisition truth. 1-500 chars.
statusNoDeal status (default 'open')
stageIdYesStage UUID within the pipeline
currencyNoISO 4217 currency code, e.g. 'USD', 'GBP', 'EUR'. Defaults to USD if omitted.
priorityNoDeal priority, e.g. 'low', 'medium', 'high'
companyIdNoAssociated company UUID
contactIdNoAssociated contact UUID
assignedToNoAssigned user (owner) UUID
pipelineIdYesPipeline UUID
probabilityNoWin probability as a 0–1 fraction (e.g. 0.75 = 75%)
customFieldsNoStructured custom-field values keyed by field key, e.g. { limit_of_indemnity: 5000000, commission_pct: 12.5 }. Define fields first with conduyt_create_custom_field.
expectedCloseDateNoExpected close date (ISO 8601, e.g. '2026-09-30')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.71.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the prerequisite IDs but says nothing about permissions required, whether creating a deal fires automations/sequences, or what happens on an invalid stageId — meaningful gaps for a mutation tool.

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

Conciseness5/5

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

Three tight sentences, front-loaded with the action, then the prerequisite, then supported capabilities. Nothing redundant and no filler.

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 14-parameter mutation tool with a nested customFields object and no output schema, the description covers prerequisites and field categories but omits the return value (does it yield a deal ID for follow-up calls?) and side effects. Adequate but with clear gaps.

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 the schema already explains all 14 parameters including the customFields example and the 0–1 probability fraction. The description only reiterates a subset (currency, probability, priority, close date, custom fields) without adding format or constraint detail 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 ('Create a new deal in a pipeline') and signals scope with 'with full attributes'. It is distinguishable from conduyt_update_deal and conduyt_import_deals by the create framing, though it never names a sibling to contrast with 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?

Explicitly states the prerequisite (pipeline and stage ID) and routes the agent to conduyt_list_pipelines to obtain them, which is the main blocker for calling this tool. No when-not-to-use guidance or mention of dedupe/pre-existing-deal behavior.

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

Deploy Server

Other Tools