Skip to main content
Glama

Create checkout link

create_print_order

Creates an unpaid print order and a checkout link for an existing draft book. The delivery address and payment are entered on inkbind.onmax.me through Stripe Checkout. Printing is conditional on payment. This call does not charge anything.

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": {
      "book_id": "<book_id>",
      "format": "<format>",
      "country": "<country>"
    },
    "name": "create_print_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
speedNo
formatYes
book_idYes
countryYesISO country code of the delivery address
quantityNoCopies of the same book to the same address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent and open-world, and the description adds real context beyond that: the order is unpaid, printing is conditional on payment, and this call charges nothing. That prevents the agent from worrying about a surprise charge. It omits the consequence of the non-idempotent hint, namely that repeated calls spawn multiple separate unpaid orders/links.

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?

Four short sentences, all front-loaded with the creation behavior and then the payment boundary. Each sentence carries distinct information: what is created, where payment happens, the payment dependency, and the no-charge guarantee. Nothing is repeated or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the agent must learn from the description what it gets back; the description says a checkout link is created but never states that the response carries that link, nor its lifetime or how to hand it to the user. Given 40% param coverage and a multi-step payment workflow, the definition is serviceable but leaves the post-call path underspecified.

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

Parameters2/5

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

Five parameters with only 40% schema description coverage. The description adds no meaning for format, speed, quantity or book_id, even though format and speed are enums whose tradeoffs (cost, delivery time) are exactly what an agent would need. Only country and quantity are documented, and that documentation lives in the schema, not the description.

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?

States a specific verb and resource: creates an unpaid print order plus a checkout link, and scopes the input to an 'existing draft book'. That is far more precise than the title alone. It does not name or differentiate against the siblings (get_order_status, layout_book, list_formats_and_prices), so the agent must infer that ordering must follow layout and precede status checks.

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?

The prerequisite that a draft book must already exist is stated, and it explains that address and payment happen on inkbind.onmax.me via Stripe Checkout, which implies this is the final step. But it never says when not to call it, what to do if a link already exists, or which sibling to call first (layout_book, list_formats_and_prices). Usage is implied rather than guided.

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