Skip to main content
Glama

Book a store order

book_store_order
Destructive

Book a same-day delivery for a WooCommerce, BigCommerce, Wix Stores or Squarespace order by its number (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 the platform if the connector has not seen it. force=true ignores the store's radius and size limits. On success the order is marked shipped / 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": {
      "platform": "<platform>",
      "order": "<order>"
    },
    "name": "book_store_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNo
orderYesOrder number like #1042, the platform's order id, or the connector's order row id
storeNoStore id, URL or key when several stores of that platform are connected
platformYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructive, open-world, non-idempotent behavior; the description adds real context on top: it may fetch the order from an external platform, it overrides store limits when forced, and success flips the order to shipped/fulfilled with a tracking link. That is meaningful side-effect disclosure beyond the hints. It stops short of saying whether repeated calls create duplicate bookings, which matters given idempotentHint=false.

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?

Four sentences, front-loaded with the action and resource, then logistics, then edge cases. Dense but each sentence carries information. Slight packing of platform list and identifier formats into one sentence costs a little readability.

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?

For a four-parameter booking tool with no output schema, the description covers the operation's scope, the external fetch fallback, the force override, and the resulting order-state change with tracking link. The only gap, the store parameter's role when multiple stores are connected, is minor against what is otherwise a complete picture.

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 50% schema coverage, the description compensates partially: it explains the order identifier format (already in schema) and adds the crucial meaning of force that the schema only gives as a bare boolean default. The platform parameter is only implied by the sentence listing platform names, and store (multi-store disambiguation) is documented nowhere in description or schema.

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 ('Book a same-day delivery') plus resource ('store order') and enumerates the supported platforms, which implicitly separates it from book_shopify_order without naming it. An agent can tell what it does at a glance, but it must infer the Shopify sibling exclusion from the platform list rather than read it directly.

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?

Clear context for use: an existing order on one of four platforms, identified by number or id, with the automatic fetch fallback noted. force=true is framed as an exception to store radius/size limits, which reads as a when-to-use condition. No explicit 'when not to use' or named alternative (e.g. create_delivery, book_shopify_order) is given.

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.