Skip to main content
Glama

Price a job at several quantities

price_quantities
Read-onlyIdempotent

The same job priced at up to 8 quantities (the price ladder), each from Printdash's pricing engine, with the delivered price when an Australian postcode is given. 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>",
      "quantities": "<quantities>"
    },
    "name": "price_quantities"
  }
}

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
quantitiesYesUp to 8 quantities, for example [250, 500, 1000, 2000].
configurationYesThe job without its quantity (any quantity given is replaced).

Output Schema

NameRequiredDescriptionDefault
nextYes
rowsYes
productYes
currencyYes
priced_forYes
product_idYes
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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. Beyond that the description adds genuinely non-obvious business context: prices originate from the pricing engine, must be relayed verbatim, delivery is Australia-only, and prices are AUD including GST — all of which an agent could not derive from annotations or schema.

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, front-loaded with the core operation, then the relay instruction, then the jurisdictional/currency caveat. No sentence is redundant and each carries information an agent needs.

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?

An output schema exists, so return values need no explanation. The description covers the key constraints an agent would otherwise get wrong: Australia-only delivery, AUD/GST pricing, exact relay of numbers, and the 8-quantity cap. What is missing is the workflow relationship — that configuration ids come from get_product and that results typically feed add_to_cart.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 80%, so the schema already explains postcode, address_id, quantities and most configuration fields. The description adds only the high-level point that the postcode yields a delivered price and that the ladder is capped at 8; it does not clarify the postcode-versus-address_id choice or what happens to a quantity passed inside configuration. Baseline 3 applies.

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?

The description states a specific verb and resource — pricing one job across up to 8 quantities via Printdash's pricing engine, with an optional delivered price from a postcode. The 'same job at several quantities' framing implicitly separates it from a single-quantity sibling, but it never names that alternative, so differentiation requires the reader to infer it from the sibling list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the 'price ladder' framing: use it when you need multiple quantity breakpoints at once. There is no explicit 'use this instead of price_job when...' routing, nor any stated precondition such as calling get_product first to obtain sizeId/stockId, even though the schema repeatedly points at get_product fields.

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