Skip to main content
Glama

Add a job to the cart

add_to_cart

Prices one job with Printdash's pricing engine (product id and a configuration of option ids, as price_job takes them) and puts it in the cart exactly as the product page's Add to cart does. If the job cannot be priced, nothing is added and the result says what is missing or the nearest combinations. Nothing is ordered or charged: checkout on printdash.io re-prices, takes artwork and payment. 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": {
      "product_id": "<product_id>",
      "configuration": "<configuration>"
    },
    "name": "add_to_cart"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_idYes
configurationYesThe job, as option ids from get_product. Everything optional: the result says what is missing.

Output Schema

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

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.6/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description discloses atomicity on pricing failure ('nothing is added and the result says what is missing'), downstream consequences (checkout re-prices, takes artwork and payment), an authentication requirement, and geographic/currency constraints (Australia only, AUD incl. GST). That is exactly the context 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?

Four sentences, front-loaded with the operation, then failure behavior, then commercial/auth caveats. Dense but each sentence carries distinct information; the final auth sentence could be folded into the commercial caveat sentence, but nothing is redundant.

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 mutating cart tool with a nested configuration and an output schema, the description covers what an agent needs: prerequisites (account), scope (Australia/AUD), failure semantics, and the fact that no order or charge occurs. Return-value detail is correctly left to the output schema.

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?

The schema covers about half the parameters in detail, and the description adds meaning the schema cannot: the configuration is 'option ids from get_product', must be shaped as price_job expects, and every sub-field is optional because the result reports what is missing. Individual optional fields still rely on schema text, but the contract-level semantics are clarified.

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?

The description names a specific verb pair and resource: price one job and place it in the cart, matching what the product page's Add to cart does. It also implicitly separates this from price_job by framing the input as 'as price_job takes them', so an agent can tell which tool actually commits the line item.

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 clear context for use: prices then adds, nothing is charged, checkout re-prices, and a signed-in account is required. It stops short of an explicit routing statement such as 'use price_job if you only want a price and no cart mutation', so the alternative is only inferable from phrasing.

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