Skip to main content
Glama

Price a print job

price_job
Read-onlyIdempotent

Prices one exact job with Printdash's pricing engine: a product id and a configuration of option ids (from get_product or match_options). Returns the price ex GST, GST and total inc GST, turnaround, a config_id and a share_url that opens the job on printdash.io; with an Australian postcode (or, signed in, a saved address id) the delivered price too. Signed in, the price is the customer's own account price. If the job cannot be priced it says what is missing, what is wrong, or the nearest combinations that can be. Relay prices exactly as returned. Printdash prints in Australia and delivers within Australia only; prices are in AUD and include GST.

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": "price_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
postcodeNoAn Australian postcode (four digits) for the delivered price. Printdash delivers within Australia only.
address_idNoSigned in: a saved address id from list_addresses, instead of a postcode.
product_idYes
configurationYesThe job, as option ids from get_product. Everything optional: the result says what is missing.

Output Schema

NameRequiredDescriptionDefault
nextYes
priceNo
errorsNo
pricedYes
reasonNo
designsNo
missingNo
nearestNo
productYes
summaryNo
currencyYes
deliveryNo
quantityNo
config_idNo
share_urlNo
product_idYes
turnaroundNo
service_areaYes
prices_include_gstYes
configuration_inputNo
quantity_per_designNo

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. Changed4 schema fields changed
    • removedOutput schema / properties / summary / properties / applied_automatically
      Removed value: -{
      -  "items": {
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
    • addedOutput schema / properties / summary / properties / extras / description
      Added value: +"The same choices as short phrases; kept for older readers, prefer options."
    • addedOutput schema / properties / summary / properties / options
      Added value: +{
      +  "description": "The other choices as the product page labels them, for example Shape: Circle or Pages: 24, in the page's order.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "label": {
      +        "type": "string"
      +      },
      +      "value": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "label",
      +      "value"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / properties / summary / required
      Previous value: -[
      -  "size",
      -  "stock",
      -  "sides",
      -  "finishing",
      -  "extras",
      -  "applied_automatically"
      -]New value: +[
      +  "size",
      +  "stock",
      +  "sides",
      +  "finishing",
      +  "extras"
      +]
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well past the readOnly/idempotent annotations: it discloses that signed-in calls return the customer's own account price, that failures report what is missing or the nearest valid combinations, and that prices must be relayed exactly as returned. It also states the jurisdiction and currency/GST constraints, which materially affect how an agent presents results.

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 paragraph is front-loaded with purpose, then returns, then error behavior, then constraints — a sensible order with no filler. It runs long for a single block and mixes in presentation instructions ("Relay prices exactly as returned"), but nearly every sentence carries information an agent would otherwise lack.

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 pricing tool with a nested configuration object, the definition covers inputs, returned fields, signed-in behavior, error outcomes, and geographic/currency limits. Even though an output schema exists, the described returns and the "nearest combinations" fallback give the agent everything needed to call and report correctly.

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 75% and the nested configuration object is already well documented, but the description still adds meaning: it ties product_id and configuration values to get_product/match_options outputs and clarifies that address_id requires being signed in and substitutes for postcode. It stops short of describing the semantics of individual configuration keys like designs or finishingIds.

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?

Opens with a specific verb and resource: "Prices one exact job with Printdash's pricing engine," and immediately scopes the inputs as a product id plus a configuration of option ids. The word "one exact job" distinguishes it from a bulk/quantity tool like price_quantities, so an agent can differentiate it without opening the 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?

Gives clear provenance guidance for inputs (option ids come "from get_product or match_options") and explains the postcode vs. signed-in address_id choice. It does not explicitly state when to prefer this over siblings such as price_quantities or create_quote, so routing to alternatives is only implied.

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