Skip to main content
Glama
Sign In
agenthouse-org

dealdesk-mcp

by agenthouse-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

dealdesk.patch_quote_share

Update a quote share link's label, password, quickchat setting, or open status. Set isOpen to false to close the customer link without deleting it.

Instructions

Update a quote share link (label, password, quickchat, or isOpen). Set isOpen=false to close the link without deleting.

Input Schema

NameRequiredDescriptionDefault
labelNo
isOpenNofalse closes the customer link
quoteIdYes
shareIdYes
passwordNoNew password, or empty/null to clear
projectIdNoDealDesk project id. Omit when the OAuth token or API key authorizes exactly one project. Required when Connect authorized several projects.
quickchatEnabledNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • 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",
-  "shareId"
-]New value: +[
+  "quoteId",
+  "shareId"
+]
  2. First observedv0.1.0

TDQS

A3.5/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 behavioral burden. It usefully discloses the non-obvious 'close without deleting' effect of isOpen=false, which is real value beyond the schema, but it omits permissions/auth needs, what happens to unrelated fields, and whether updates are reversible.

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?

Two tight sentences, front-loaded with the operation and then the key field behavior. No filler; every clause earns its place.

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 mutation tool with no annotations, no output schema, and only 43% param coverage, the description is adequate but leaves gaps: it never explains the projectId authorization model or the identifier requirements, both of which an agent needs to call it correctly.

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 43% (below 50%), so the description must compensate. It names four of seven fields (label, password, quickchat, isOpen), mapping 'quickchat' to quickchatEnabled, but adds nothing for projectId or quoteId/shareId, and the important multi-project projectId semantics appear only in 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 (Update) and resource (quote share link) plus the four mutable fields, which distinguishes it from create_quote_share and list_quote_shares by name resemblance. It does not explicitly name those siblings, but the 'patch/update' framing is unambiguous.

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?

'Set isOpen=false to close the link without deleting' is genuine when/how guidance for one field, implying this tool is preferred over deletion for closing a link. However, there is no guidance on when to use this versus create_quote_share or other share operations, so usage is only partially covered.

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