Skip to main content
Glama

create_order

Place an order for a service. Needs credentials. Returns the order id, the offer and an accessToken you must keep for the following calls. The offer is pinned to the hash of the service page; accept_offer needs offer.version and offer.terms..hash from it. Services without a catalogue price return an offer with no total and wait for a person to price it. Errors: MISSING_ when a required brief field is absent, UNEXPECTED_FIELD when the brief has a key the service does not declare.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
briefYesRequired MCP argument: send an object, including {} when the selected service has no required brief fields. Direct REST may omit brief and treats that as {}; required catalog fields remain mandatory. One string per field the catalogue lists under this service in catalog.services.<service>.fields. Use each field id as the key. Fields with required: true must be present; the max value is the length limit. No other keys are accepted.
linesNoOnly for services that have catalog.services.<service>.configurator. One entry per item: item is an id from configurator.items; qty is the number of designs, or the number of pages when the item has per "page", within item.qty min and max; options maps every option id of the item to one of its value ids; note is free text, required when the item has noteRequired. The price is computed by the seller from the catalogue; never send a price. If any chosen item has price null, the order waits for a person to price it.
secretNoRequired unless you authenticate with the Authorization header (Bearer <clientId>:<secret>, or an OAuth access token issued for this server). The secret returned by register_agent.
serviceYesService id: one of the keys of catalog.services, as returned by the catalog tool.
clientIdNoRequired unless you authenticate with the Authorization header (Bearer <clientId>:<secret>, or an OAuth access token issued for this server). The clientId returned by register_agent.
languageNoLanguage of the offer, the terms and the documents. This MCP adapter defaults to en; direct REST requires payload.language explicitly.en
printQuoteNoOnly with lines: the buyer would like a print quote once the design work has started. Printing is not part of this order.
idempotencyKeyNoYour own stable key, 16-100 characters, so a repeated call does not create a second order. If omitted this MCP adapter generates a new key for each invocation; provide and reuse a key for retries. Direct REST always requires idempotencyKey.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / brief / description
      Previous value: -"One string per field the catalogue lists under this service in catalog.services.<service>.fields. Use each field id as the key. Fields with required: true must be present; the max value is the length limit. No other keys are accepted."New value: +"Required MCP argument: send an object, including {} when the selected service has no required brief fields. Direct REST may omit brief and treats that as {}; required catalog fields remain mandatory. One string per field the catalogue lists under this service in catalog.services.<service>.fields. Use each field id as the key. Fields with required: true must be present; the max value is the length limit. No other keys are accepted."
    • changedInput schema / properties / idempotencyKey / description
      Previous value: -"Your own key, so a repeated call does not create a second order."New value: +"Your own stable key, 16-100 characters, so a repeated call does not create a second order. If omitted this MCP adapter generates a new key for each invocation; provide and reuse a key for retries. Direct REST always requires idempotencyKey."
    • addedInput schema / properties / language / default
      Added value: +"en"
    • changedInput schema / properties / language / description
      Previous value: -"Language of the offer, the terms and the documents. Defaults to en."New value: +"Language of the offer, the terms and the documents. This MCP adapter defaults to en; direct REST requires payload.language explicitly."
  2. Changed2 schema fields changed
    • addedInput schema / properties / lines
      Added value: +{
      +  "description": "Only for services that have catalog.services.<service>.configurator. One entry per item: item is an id from configurator.items; qty is the number of designs, or the number of pages when the item has per \"page\", within item.qty min and max; options maps every option id of the item to one of its value ids; note is free text, required when the item has noteRequired. The price is computed by the seller from the catalogue; never send a price. If any chosen item has price null, the order waits for a person to price it.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "item": {
      +        "type": "string"
      +      },
      +      "note": {
      +        "maxLength": 500,
      +        "type": "string"
      +      },
      +      "options": {
      +        "additionalProperties": {
      +          "type": "string"
      +        },
      +        "type": "object"
      +      },
      +      "qty": {
      +        "type": "integer"
      +      }
      +    },
      +    "required": [
      +      "item"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 20,
      +  "type": "array"
      +}
    • addedInput schema / properties / printQuote
      Added value: +{
      +  "description": "Only with lines: the buyer would like a print quote once the design work has started. Printing is not part of this order.",
      +  "type": "boolean"
      +}
  3. Changed6 schema fields changed
    • addedInput schema / properties / brief / additionalProperties
      Added value: +{
      +  "type": "string"
      +}
    • changedInput schema / properties / brief / description
      Previous value: -"The fields the catalogue declares for this service."New value: +"One string per field the catalogue lists under this service in catalog.services.<service>.fields. Use each field id as the key. Fields with required: true must be present; the max value is the length limit. No other keys are accepted."
    • changedInput schema / properties / clientId / description
      Previous value: -"Your client identifier, if not sent in the Authorization header."New value: +"Required unless you authenticate with the Authorization header (Bearer <clientId>:<secret>, or an OAuth access token issued for this server). The clientId returned by register_agent."
    • changedInput schema / properties / language / description
      Previous value: -"Language of the offer and the documents. Defaults to en."New value: +"Language of the offer, the terms and the documents. Defaults to en."
    • changedInput schema / properties / secret / description
      Previous value: -"Your secret, if not sent in the Authorization header."New value: +"Required unless you authenticate with the Authorization header (Bearer <clientId>:<secret>, or an OAuth access token issued for this server). The secret returned by register_agent."
    • changedInput schema / properties / service / description
      Previous value: -"Service identifier from the catalogue."New value: +"Service id: one of the keys of catalog.services, as returned by the catalog tool."
  4. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already mark this as non-read-only, non-idempotent and non-destructive, and the description adds substantial context beyond them: the auth requirement, that the caller must retain accessToken for follow-up calls, that the offer is hash-pinned, that some orders stall awaiting human pricing, and the MISSING_<field>/UNEXPECTED_FIELD error contract. The idempotencyKey explanation is consistent with idempotentHint=false (retries need a reused key) rather than contradicting it.

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?

Dense and front-loaded: purpose first, then return contract, then pricing edge case, then error codes. Every sentence carries information, though the back half is run-on and could be split for scanability.

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?

With no output schema, the description correctly compensates by describing the return values (order id, offer, accessToken and its retention requirement). Combined with the error contract, idempotency guidance and human-pricing branch for an 8-parameter, nested-schema tool, it covers what an agent needs 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%, so all eight parameters are already documented in the schema; baseline is 3. The description adds only marginal param detail (brief field-absence errors, language default, offer.terms.<language>.hash linkage), so it does not clearly exceed the structured data.

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+resource ('Place an order for a service') and immediately distinguishes it from siblings by describing the offer/accessToken handoff that feeds accept_offer. An agent can tell it apart from order_status, start_payment and accept_offer 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 sequencing context: credentials are needed (pointing to register_agent), the returned offer fields are what accept_offer consumes, and services with no catalogue price wait for a human. It does not state explicit when-not or compare against a sibling like accept_offer/order_status directly, but the workflow conditions are clear.

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