Skip to main content
Glama

Prepare an order

create_order

Prepares an order for your user to approve and pay. Returns approvalUrl (give it to the user: they review the terms, consent and pay there; you cannot) and a private token for get_order_status. Nothing is charged until the user pays, and only when the certificate is issued.

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": {
      "files": "<files>"
    },
    "name": "create_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesYesOne PDF, or up to 5 JPEG/PNG images of one document in page order. Max 10 MB in total before encoding (base64 in JSON makes it about a third larger; the REST API takes up to 20 MB as a multipart upload).
namesNoOptional, up to 10 people named in the document: added to the translation as a customer-supplied note (names in the translation stay as written)
localeNoLanguage of the user's pages and emails (Japanese if omitted), and of this tool's messages (English if omitted)
receiving_procedureNoWhere the translation will be submitted, if known

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / files / description
      Previous value: -"One PDF, or up to 5 JPEG/PNG images of one document in page order. Max 10 MB in total."New value: +"One PDF, or up to 5 JPEG/PNG images of one document in page order. Max 10 MB in total before encoding (base64 in JSON makes it about a third larger; the REST API takes up to 20 MB as a multipart upload)."
    • removedInput schema / properties / locale / default
      Removed value: -"ja"
    • changedInput schema / properties / locale / description
      Previous value: -"Language of the user's pages and emails"New value: +"Language of the user's pages and emails (Japanese if omitted), and of this tool's messages (English if omitted)"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations it discloses the charging model ('nothing is charged until the user pays, and only when the certificate is issued'), the human-consent handoff, and that the returned token is private. It omits what happens on repeated calls (relevant given idempotentHint=false) and whether orders expire, so it stops short of full behavioral disclosure.

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 tight sentences, front-loaded with the action and return values, then the constraint that the agent cannot complete payment. Every clause carries information an agent needs.

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?

No output schema exists, yet the description names both return values (approvalUrl, token) and their handling, and clarifies cost timing. Combined with a fully documented 4-parameter schema, an agent has everything needed to call it correctly.

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%, with per-field detail on files, names, locale, and receiving_procedure, so the schema carries the parameter burden. The description adds no parameter-level guidance of its own, making 3 the correct baseline.

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 ('Prepares an order') plus the essential qualifier that the user, not the agent, completes it. It contrasts with siblings by naming get_order_status as the consumer of the returned token, so an agent can distinguish this from quote_document and get_order_status without opening a 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 operational context: hand approvalUrl to the user, the agent cannot pay, and the token feeds get_order_status. It does not explicitly say when to prefer this over quote_document (e.g. quote first, order when the user is ready to pay), so that one routing decision is left implicit.

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