Skip to main content
Glama

order_create

Create an unpaid draft order with quotes: uploads and checks the PDF, validates the address and returns a quote per shipping method. Nothing is bought; use order_purchase for that.

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": {
      "file": "<file>",
      "product": "<product>",
      "qty": "<qty>",
      "ship_to": "<ship_to>"
    },
    "name": "order_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
qtyYesQuantity; must be one the product offers.
fileYesPrint-ready PDF, as an https URL it can be downloaded from (at most 32 MB), or the id (fil_…) of a file sent before.
foldNoFilter by fold.
noteNoYour note, kept on the order.
sizeNoFilter by size.
sidesNoFilter by sides.
stockNoFilter by stock.
finishNoFilter by finish.
optionNoFilter by any option, as key=value. Repeatable.
pickupNoCollect from a pickup point instead of door delivery: a pkp_… id from `pickup-points`, "nearest", or "door" to switch back.
productYesProduct id or alias, e.g. flyer.
ship_toYesDelivery address: a JSON file, inline JSON, or - for stdin. As an object: US {name, line1, city, state, postal_code}; Hong Kong {name, line1, district, area, phone, email, country: "HK"}.
max_totalNoBudget in the order's currency (USD, in the US and Hong Kong), e.g. 450; quotes above it are flagged.
client_refNoYour reference; re-running create with the same one returns the same order.
deliver_byNoDeadline (YYYY-MM-DD); used to rank quotes, never a guarantee.
orientationNoFilter by orientation.

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
errorNo
summaryNo
warningsNo
next_actionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare non-read-only, open-world, non-destructive behavior, so the bar is lower, and the description still adds real context: it uploads and validates the supplied PDF, validates the delivery address, and produces quotes without committing a purchase. It does not mention that re-running with the same client_ref returns the same order, which is a notable omission given idempotentHint=false in the annotations.

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?

Two sentences, front-loaded with the action and its scope, then the exclusion. Every clause carries information; there is no filler or repetition of the title.

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?

With 16 parameters, an output schema, and rich annotations, the description covers the workflow shape and the safety profile adequately, so return values need not be explained. The gap is the client_ref idempotency behavior, which matters for a creation tool and is left to the schema alone.

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 100%, so the baseline is 3. The description adds behavioral meaning to the two most consequential inputs — the file is uploaded and checked, ship_to is validated — but says nothing about qty/product/option/max_total/deliver_by semantics beyond what the schema already states.

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 gives a specific verb and resource ('Create an unpaid draft order') and enumerates the concrete sub-actions performed: PDF upload and check, address validation, and one quote per shipping method. It explicitly separates itself from the purchasing sibling, so an agent can distinguish it from order_purchase without opening either 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?

It states the boundary clearly: 'Nothing is bought; use order_purchase for that' names the alternative and the condition that selects it. It is weaker on the quoting siblings — since this tool already 'returns a quote per shipping method', an agent gets no guidance on when to use order_quote or order_wait instead, which is the one remaining routing ambiguity.

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