Skip to main content
Glama

Change a job in the cart

update_cart_line
DestructiveIdempotent

Changes one cart line's options (only what is given: a new quantity, stock, finish or size) and re-prices it with the pricing engine. A line from a quote Printdash priced 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": {
      "line_id": "<line_id>",
      "configuration": "<configuration>"
    },
    "name": "update_cart_line"
  }
}

Input Schema

NameRequiredDescriptionDefault
line_idYesA line_id from get_cart.
configurationYesOnly the options that change, as option ids: a new quantity, stock, finishing ids or size. Finishing ids replace the line's finishing.

Output Schema

NameRequiredDescriptionDefault
cartNo
nextYes
addedNo
priceNo
errorsNo
pricedNo
reasonNo
line_idNo
missingNo
nearestNo
productYes
updatedNo
currencyYes
product_idYes
turnaroundNo
service_areaYes
prices_include_gstYes
configuration_inputNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / 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 / configuration / properties / stickerShape / enum
      Previous value: -[
      -  "square",
      -  "circle",
      -  "custom"
      -]New value: +[
      +  "square",
      +  "rectangle",
      +  "circle",
      +  "custom"
      +]
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses the re-pricing side effect, the partial-update contract ("only what is given"), a hard business restriction on quote-priced lines, and the auth requirement including what happens when unauthenticated (the connection prompts sign-in on printdash.io). This is exactly the context destructiveHint=true alone cannot convey.

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 sentences, each carrying distinct load: what changes and how, the exclusion, then the auth requirement. Front-loaded with the action, no filler or restatement of the title.

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?

For a two-parameter mutation tool with a rich nested schema, full annotation coverage and an output schema, the description supplies the remaining behavioral facts an agent needs: partial-update semantics, re-pricing, ineligibility of quote-priced lines, and the sign-in flow. Nothing material is left to inference.

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?

Schema coverage is 100%, so the baseline is 3; the description earns an extra point by foregrounding that only supplied options change and by naming the mutable dimensions (quantity, stock, finish, size) at the tool level, so an agent understands the partial-update model without opening the nested schema. It does not add format or cross-field details beyond that.

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 ("changes one cart line's options") plus the side effect ("re-prices it with the pricing engine"). Read against siblings like add_to_cart, remove_cart_line and price_job, it is unambiguous that this mutates an existing line and re-prices as part of the change.

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?

Gives a clear precondition (the line must already exist and come from get_cart's line_id) and an explicit exclusion: "A line from a quote Printdash priced cannot be changed." It does not name a fallback tool for that excluded case or point to add_to_cart for creating a new line, so routing guidance is strong but not complete.

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