Skip to main content
Glama

Price an order's job again

reorder
Read-onlyIdempotent

Turns one job from a past order (item_id from get_order, where can_reorder is true) back into a configuration and prices it at today's price, optionally at another quantity, exactly as price_job does. Writes nothing: add_to_cart with its product_id and configuration_input puts it in the cart. Jobs priced by Printdash's team (reorder_by_request) go through request_reorder instead. 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": {
      "order": "<order>"
    },
    "name": "reorder"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderYesThe order number (or the order id from its link).
item_idNoThe job's item_id from get_order (optional on a one-job order).
quantityNoAnother quantity; omit for the same.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
      +]
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/idempotent/non-destructive, and the description reinforces this with a concrete consequence — 'writes nothing' — plus where the state actually goes (add_to_cart). It adds context annotations cannot carry: an auth requirement (signed-in Printdash account, sign-in prompt on printdash.io) and commercial scope (Australia-only delivery, AUD prices including GST).

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?

Front-loaded with the core action and effect in the first two sentences; routing, auth and locale follow. Dense but each sentence carries distinct information, though the Australia/AUD/GST sentence reads as server-wide boilerplate that a frequent caller pays for on every read.

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 exists, so return values needn't be explained, yet the description still hands the agent the two fields it needs downstream (product_id, configuration_input). Combined with auth, region, currency, sibling routing and the write-nothing guarantee, nothing needed to call it correctly is missing.

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 baseline is 3, but the description adds genuine meaning: item_id is sourced from get_order and only optional on a one-job order, and quantity means 'priced at another quantity, exactly as price_job does' rather than a mutation. It does not restate format constraints for order, which the schema already handles.

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 — turning one job from a past order back into a configuration and pricing it at today's price — and pins the scope (single job, current price, optional new quantity). It explicitly distinguishes itself from the near-identical price_job, from request_reorder, and from add_to_cart, so an agent can separate it from all three siblings.

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

Usage Guidelines5/5

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

Gives an explicit precondition (item_id from get_order where can_reorder is true), an explicit exclusion and alternative (jobs priced by Printdash's team go through request_reorder), and an explicit next step (add_to_cart with product_id and configuration_input). When-to-use, when-not-to-use and the follow-up are all named rather than inferred.

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