Skip to main content
Glama

Save a quote

create_quote

Saves a new quote with a quote number from up to 20 jobs (each a product id and configuration, priced by the engine first), with an optional saved address for delivery, pickup where the account has it, an order reference and notes. Prices are locked for 30 days. It is the customer's saved quote, ready to share with a client (share_quote, email_quote) or convert to an order. If a job cannot be priced, nothing is saved. Printdash prints in Australia and delivers within Australia only; prices are in AUD and include GST. 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": {
      "lines": "<lines>"
    },
    "name": "create_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
linesYesThe jobs, each priced by the engine before anything is saved.
notesNo
referenceNoThe customer's order reference or job name.
address_idNoA saved address id for delivery (list_addresses). Omit to choose at checkout.
fulfilmentNopickup only where the account has pickup (estimate_delivery says pickup_available).

Output Schema

NameRequiredDescriptionDefault
urlNo
nextYes
linesNo
savedYes
errorsNo
pickupNo
pricedNo
reasonNo
statusNo
expiresNo
missingNo
nearestNo
productNo
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.
shipping_ex_gstNo
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.6/5.0
Behavior5/5

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

Beyond the annotations (write, non-idempotent, closed-world), the description discloses what the annotations cannot: pricing runs before any save, a failed price means nothing is saved (atomicity), prices are locked for 30 days, and unauthenticated calls trigger a sign-in prompt rather than a silent failure. Geographic and currency scope are also stated, which materially affects whether calling it is appropriate at all.

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?

The first sentence carries the core action and cardinality, later sentences layer constraints, and nothing is repeated from the schema verbatim. The opening sentence is long and parenthetical-heavy, which costs a little scannability, but every clause adds a fact an agent needs.

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

Completeness5/5

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

An output schema covers return values, so the description correctly spends its budget on the things not encoded elsewhere: auth behavior, geo/currency scope, price lock duration, the all-or-nothing save semantics, and how the quote feeds into share/email/convert. Nothing material is missing for a 5-parameter creation tool.

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 80% schema description coverage the baseline is 3, and the description earns more by adding meaning the schema doesn't: the 20-job cap, that each job is a product id plus configuration pre-priced by the engine, that address_id is a delivery address omitted to choose at checkout, and that pickup is only valid where estimate_delivery reports pickup_available. That pickup constraint in particular is an operational rule absent from the enum itself.

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?

"Saves a new quote with a quote number from up to 20 jobs" states a specific verb, resource, and unit of work, and it distinguishes itself from siblings by naming share_quote, email_quote, and conversion to order as downstream steps. An agent can tell this apart from update_quote or request_custom_quote without opening any schema.

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 gives the context that selects this tool (a customer quote that will later be shared or converted) plus hard prerequisites: a signed-in Printdash account, Australia-only delivery, AUD prices including GST. It does not explicitly exclude the nearby alternatives (update_quote for existing quotes, request_custom_quote when a job can't be priced automatically), so the routing guidance is clear but not exhaustive.

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