Wayfront

Deal Write Tool

deal-write

Destructive

Create, partially update, mark_won, mark_lost or reopen sales deals. Create requires user_id, pipeline_id, stage_id and title; value and service_id are optional. It creates the deal and first pipeline card together. Separate opportunities under one contact are allowed. Update preserves omitted fields, can reassign user_id to another active client contact, and accepts null to clear company_id, owner_id, service_id, value or expected_close_date. Reassignment moves existing activities and the conversation to the new contact while invoices retain their original client. Closed deals lock value and service. Closing a deal also closes its conversation ticket and can trigger configured integrations. Use pipeline-item-write to move cards and deal-activity-write with deal_id to record deal activities. Use deal-message-write to send client-facing messages. Does not delete deals.

Input Schema

Name	Required	Description
`note`	No	Optional first private activity, max 10000 characters. Create only; requires permission to create activities for the contact.
`title`	No	Opportunity title, max 255 characters. Required for create; optional for update.
`value`	No	Optional nonnegative decimal amount, e.g. "1250.00". Requires invoice access; zero is allowed. Null clears on update. Locked once closed.
`action`	Yes
`deal_id`	No	Required for update, mark_won, mark_lost and reopen.
`user_id`	No	Existing active client contact ID. Required for create; optional on update to reassign the deal and its conversation while preserving history. Multiple deals may use the same contact.
`owner_id`	No	Staff owner ID. Create defaults to the authenticated user; null unassigns on update.
`stage_id`	No	Stage in that pipeline. Required for create. Move existing cards with pipeline-item-write.
`company_id`	No	Optional company owned by or containing the contact. Null clears it on update. An unknown end-client does not require a company.
`service_id`	No	Optional active service. Supplies the price/currency when value is omitted. Null clears on update. Locked once closed.
`lost_reason`	No	Optional reason for mark_lost, max 255 characters.
`pipeline_id`	No	Visible sales pipeline ID. Required for create.
`expected_close_date`	No	Optional date, YYYY-MM-DD. Null clears on update.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 31, 2026

changedInput schema / properties / service_id / description

Previous value: -"Optional active service. Supplies the price/currency when value is omitted. Required on create without invoice access. Null clears on update. Locked once closed."New value: +"Optional active service. Supplies the price/currency when value is omitted. Null clears on update. Locked once closed."

changedInput schema / properties / value / description

Previous value: -"Nonnegative decimal amount, e.g. \"1250.00\". Requires invoice access. Create requires value or service_id; zero is allowed. Null clears on update. Locked once closed."New value: +"Optional nonnegative decimal amount, e.g. \"1250.00\". Requires invoice access; zero is allowed. Null clears on update. Locked once closed."

Changed1 schema field changedOct 14, 2026

changedInput schema / properties / user_id / description

Previous value: -"Existing client contact ID. Required for create; cannot be changed later. Multiple deals may use the same contact."New value: +"Existing active client contact ID. Required for create; optional on update to reassign the deal and its conversation while preserving history. Multiple deals may use the same contact."

AddedOct 13, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Rich behavioral disclosure well beyond the terse annotations: create builds the deal and first pipeline card together, update preserves omitted fields and accepts nulls to clear, reassignment moves activities and conversation while invoices stay with the original client, closed deals lock value/service, and closing also closes the conversation ticket and may fire integrations. The only gap is no note on permissions/auth scope for the mutating actions.

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?

Front-loaded with the action verbs and create requirements, then organized by behavior. It is dense and long, but nearly every sentence carries operational meaning; slightly more structure (e.g. per-action grouping) would help scanning.

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

Completeness5/5

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

For a 13-parameter multi-action mutation tool with no output schema and only coarse annotations, the description covers creation prerequisites, update/null semantics, side effects of closing and reassignment, and non-deletion scope — leaving no critical gap for an agent to call it correctly.

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 92%, so the schema already documents most parameters (baseline 3). The description adds meaning beyond it — which fields are create-required, the null-clears-on-update semantics, reassignment effects on activities/invoices, and lock-on-close — pushing it above baseline.

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?

Opens with a specific set of verbs (create, update, mark_won, mark_lost, reopen) on a named resource (sales deals), and each action's required fields are spelled out. It explicitly distinguishes itself from nearby siblings like pipeline-item-write, deal-activity-write, and deal-message-write.

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?

It states which sibling to use for card moves, activity recording, and client messaging, and closes with an explicit exclusion ('Does not delete deals'). The when-to-use boundaries are fully inferable from the text.

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

All Wayfront tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?