Skip to main content
Glama
agenthouse-org

dealdesk-mcp

dealdesk.duplicate_quote_preset

Duplicate a quote preset. The copy name is the source name plus " copy".

Instructions

Duplicate a quote preset. The copy name is the source name plus " copy".

Input Schema

NameRequiredDescriptionDefault
presetIdYes
projectIdNoDealDesk project id. Omit when the OAuth token or API key authorizes exactly one project. Required when Connect authorized several projects.

Output Schema

NameRequiredDescriptionDefault
presetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

C2.9/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 does add one genuinely useful behavioral fact — the copy is named source name plus " copy" — but omits what is copied (items, prices, sharing), whether the copy is independent, and error behavior for an unknown presetId.

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?

Two short sentences with no filler, and the action is stated first followed by the naming rule. Efficient, though it is so terse that it omits content rather than being optimally concise.

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

Completeness2/5

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

A mutation tool with no annotations and an undocumented required parameter; the description covers the action and resulting name but nothing about what state is copied or what the response contains. The existing output schema offsets return-value concerns only slightly, leaving meaningful gaps for a write operation.

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 50%: projectId is documented in the schema but presetId has no description anywhere. The description never explains that presetId identifies the source preset to copy, so it does not compensate for the coverage gap on the required parameter.

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 ("Duplicate") and resource ("quote preset"), so an agent can tell what it does. However, it does not distinguish itself from nearby siblings like create_quote_preset_from_quote or clone_quote, leaving ambiguity about which copy mechanism to pick.

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

Usage Guidelines2/5

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

No guidance on when to duplicate versus use create_quote_preset_from_quote or apply_quote_preset, and no prerequisites or exclusions. The only context given is the resulting name convention, which is not usage guidance.

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