dealdesk-mcp

dealdesk.update_quote_from_configuration

Re-apply a published Portfolio configuration to an existing draft quote, replacing commercial details while keeping title, customer, and ownership. Optionally reshape presentation via quote layout.

Instructions

Re-apply a published Portfolio configuration onto an existing draft quote (full commercial replace). Does not change title/customer/ownership. Optional quoteLayout reshapes presentation.

Input Schema

Name	Required	Description
`locale`	No
`quoteId`	Yes
`currency`	No
`projectId`	No	DealDesk project id. Omit when the OAuth token or API key authorizes exactly one project. Required when Connect authorized several projects.
`quoteLayout`	No
`configuration`	Yes	CPQ configuration with selections[] and optional context
`portfolioRevisionId`	Yes
`priceBookRevisionId`	Yes

Output Schema

Name	Required	Description	Default
`quote`	Yes	Quote status, totals, and optional analytics/shares. Extra fields live on this object, not beside it.
`idempotentReplay`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.1.1Oct 7, 2026

changedInput schema / properties / projectId / description

Previous value: -"DealDesk project id (must match API key / OAuth project)"New value: +"DealDesk project id. Omit when the OAuth token or API key authorizes exactly one project. Required when Connect authorized several projects."

changedInput schema / required

Previous value: -[
-  "projectId",
-  "quoteId",
-  "portfolioRevisionId",
-  "priceBookRevisionId",
-  "configuration"
-]New value: +[
+  "quoteId",
+  "portfolioRevisionId",
+  "priceBookRevisionId",
+  "configuration"
+]

changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +true
```

changedOutput schema / properties / quote / description

Previous value: -"Quote summary shown in the quote-totals widget"New value: +"Quote status, totals, and optional analytics/shares. Extra fields live on this object, not beside it."

First observedv0.1.0Sep 30, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the key mutation semantics: a 'full commercial replace' (destructive to existing commercial content) while preserving title/customer/ownership, plus the optional quoteLayout reshaping presentation. It omits auth/permission requirements and reversibility, so it stops short of full coverage.

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 with the operation and its destructive scope front-loaded, then the preservation guarantee, then the optional presentation parameter. No filler and nothing buried.

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?

The output schema means return values need no explanation, and the behavioral scope (what is replaced vs preserved) is covered. However, for an 8-parameter, nested-object mutation tool with no annotations and 25% schema coverage, the near-total silence on parameter meanings leaves a real gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 25%, so the description must compensate, yet it only adds meaning for quoteLayout ('reshapes presentation'). quoteId, portfolioRevisionId, priceBookRevisionId, locale, currency, and projectId get no explanation beyond the schema, and even the required 'configuration' object is not elaborated on here.

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?

States a specific verb ('Re-apply'), the resource (a published Portfolio configuration), and the target (an existing draft quote), with a parenthetical that names the operation mode ('full commercial replace'). The phrase 'existing draft quote' cleanly distinguishes it from the sibling create_quote_from_configuration and from replace_quote_items.

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

Usage Guidelines3/5

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

Usage is implied by 'onto an existing draft quote' and bounded by 'Does not change title/customer/ownership', but no alternative sibling is named and there is no explicit when-not guidance. An agent can infer the context but is not routed to a decision.

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

Deploy Server