Skip to main content
Glama

Book a Shopify order

book_shopify_order
Destructive

Book a same-day delivery for a Shopify order by its name (e.g. #1042) or id. Pickup is the store location, drop-off the order's shipping address, items from the line items. Fetches the order from Shopify if the app has not seen it. force=true ignores the shop's radius and size limits. On success the order is fulfilled with a tracking link as the driver picks it up.

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": "book_shopify_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
shopNomyshopify.com domain when several shops are connected
forceNo
orderYesOrder name like #1042, Shopify order id, or the app's order row id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the data mapping (pickup = store location, drop-off = shipping address, items = line items) and the key side effect: on success the order is fulfilled with a tracking link. That confirms and enriches the destructiveHint=true annotation rather than contradicting it. It stops short of stating permission requirements, failure modes, or whether a failed booking leaves anything partially applied.

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?

Three tight sentences, front-loaded with the action and accepted identifier formats, then the implicit data mapping, then the escalation flag. 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?

For a 3-parameter, single-required-parameter booking tool with no output schema, the description covers identifiers, source of truth, derived fields, the force override, and the resulting fulfillment. The only meaningful gap is what the agent should expect on failure or when multiple shops are connected, which is partly handled by the shop parameter description in the schema.

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?

With 67% schema coverage, the schema already documents shop and order; the description's main added value is explaining force=true ignores the shop's radius and size limits, which the schema leaves as an undocumented boolean default. It adds no detail on the shop parameter (multi-shop selection) beyond what the schema says.

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: 'Book a same-day delivery for a Shopify order by its name (e.g. #1042) or id', with a concrete example identifier. The Shopify qualifier implicitly separates it from the generic book_store_order sibling, but the description never names that alternative, so the routing is inferred rather than stated.

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?

Usage is implied by the scenario ('same-day delivery for a Shopify order') and the description notes it will fetch the order from Shopify if unseen, which tells the agent it need not pre-sync. There is no explicit when-not guidance and no mention of book_store_order or other alternatives, leaving the agent to decide between Shopify-specific and generic booking on its own.

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.