Skip to main content
Glama

Change a saved quote

update_quote
DestructiveIdempotent

Changes a saved quote in place: lines to change (line_id plus only the options that change) or add (product_id and configuration), lines to remove, the reference, notes or delivery address. Changed and added lines are re-priced by the engine; untouched lines keep their prices. Accepted, ordered, expired and team-priced quotes cannot be changed. Needs a signed-in Printdash account: called without one, the connection asks the customer to sign in on printdash.io.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "quote": "<quote>"
    },
    "name": "update_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
linesNo
notesNo
quoteYesThe quote number (or the quote id from its link).
referenceNo
address_idNoA saved address id, or null to clear it.
remove_line_idsNo

Output Schema

NameRequiredDescriptionDefault
urlNo
nextYes
linesNo
errorsNo
pickupNo
pricedNo
reasonNo
statusNo
expiresNo
missingNo
nearestNo
productNo
updatedYes
currencyYes
referenceNo
share_urlNo
line_indexNo
product_idNo
quote_numberNo
service_areaYes
status_labelNo
total_inc_gstNoThe quote page's Total, inc GST: subtotal_inc_gst (the lines) plus delivery (shipping_ex_gst) and its GST.
added_line_idsNo
shipping_ex_gstNo
changed_line_idsNo
removed_line_idsNo
subtotal_inc_gstNo
prices_include_gstYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / lines / items / properties / configuration / properties / stickerShape / description
      Added value: +"Where get_product has a sticker_shape field: an id from it. Stickers: square, circle or custom; labels: rectangle, circle or custom."
    • changedInput schema / properties / lines / items / properties / configuration / properties / stickerShape / enum
      Previous value: -[
      -  "square",
      -  "circle",
      -  "custom"
      -]New value: +[
      +  "square",
      +  "rectangle",
      +  "circle",
      +  "custom"
      +]
  2. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the annotations (which only mark it non-read-only, destructive, idempotent): it discloses that changed and added lines are re-priced by the engine while untouched lines keep their prices, lists the quote states that block the operation, and specifies the sign-in requirement and the fallback prompt on printdash.io. That is exactly the kind of consequence and precondition detail annotations cannot carry.

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 mutation verb and scope, then the field list, then behavioral caveats, then auth. Every sentence carries information. The opening sentence is dense and slightly list-like, but nothing is redundant enough to cut.

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

Completeness4/5

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

For a 6-parameter destructive mutation with an output schema available, the description covers purpose, preconditions, pricing side effects and auth. The only notable omissions are whether removed lines are permanently lost and how pricing errors on changed lines surface, both of which an agent would want before calling.

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?

With only 33% schema coverage across 6 parameters, the description compensates by mapping each argument to its purpose: lines (line_id plus only changed options, or product_id plus configuration for adds), lines to remove, reference, notes, delivery address. The partial-update semantics are the key insight and are stated in prose, though some of it duplicates the nested schema descriptions.

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?

"Changes a saved quote in place" gives a specific verb and resource, and the following clause enumerates exactly what can be altered (change/add/remove lines, reference, notes, delivery address). An agent can distinguish this from create_quote or delete_quote by the in-place mutation wording, though no sibling is named explicitly.

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?

Provides a clear when-not: accepted, ordered, expired and team-priced quotes cannot be changed, which is a strong negative precondition. It also states the authentication requirement. It stops short of naming an alternative tool for those blocked cases (e.g. duplicate_quote or convert_quote_to_order), leaving the redirect to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources