Skip to main content
Glama
Sign In
agenthouse-org

dealdesk-mcp

by agenthouse-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

dealdesk.create_quote_share

Create a customer share link for a quote, returning standard and rich experience paths. Deactivate later with isOpen=false; deletion isn't available through MCP.

Instructions

Create a customer share link for a quote. Returns classicPath (standard share) and experiencePath (rich experience). Soft-close later with patch_quote_share isOpen=false; delete is not available through MCP.

Input Schema

NameRequiredDescriptionDefault
labelNo
quoteIdYes
passwordNoOptional share password
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"
-]New value: +[
+  "quoteId"
+]
  2. First observedv0.1.0

TDQS

A4/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 useful traits: the two returned link types (classicPath, experiencePath), the soft-close mechanism, and the absence of a delete path. It omits permission/auth requirements, whether the link is immediately live, and password enforcement behavior.

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 short sentences, front-loaded with the action, then return values, then lifecycle constraints. No filler; every sentence adds information.

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, so disclosing classicPath/experiencePath is genuinely necessary and provided. However, for a 5-parameter mutation with no annotations and 40% schema coverage, key context (auth/project scoping, password behavior, quickchatEnabled semantics) is missing.

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 description coverage is only 40% (label, quoteId, and quickchatEnabled are undocumented), and the description compensates for none of it — it never explains label, password, quickchatEnabled, or projectId. The agent must infer all parameter meaning from the schema alone.

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 and resource ('Create a customer share link for a quote') that an agent can immediately distinguish from siblings like list_quote_shares, patch_quote_share, and create_quote. The scope 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 Guidelines4/5

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

It routes the agent clearly for the follow-up lifecycle: 'Soft-close later with patch_quote_share isOpen=false' names the alternative tool and the exact operation, and it warns that delete is unavailable through MCP. It stops short of stating when creating a share is or isn't appropriate (e.g. prerequisites on quote state).

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