Skip to main content
Glama
WebCake Storefront MCP

WebCake Storefront MCP

by vuluu2k

order

Read-only

Retrieve store purchases and customer records: list or filter purchases, fetch full details by ID, and find customers by ID, phone, or email.

Instructions

Orders and customers. Pick the operation with action and pass that action's arguments (help:true returns its full documentation and schema).

  • list_orders: List orders of the site (metadata only).

  • get_order: Get full order details by ID: customer info, items, payment, shipping, discounts, etc.

  • list_customers: List/search the site's customers (browse or segment).

  • find_customer: Find a customer by ID, phone number, or email

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": {
      "action": "<action>"
    },
    "name": "order"
  }
}

Input Schema

NameRequiredDescriptionDefault
byNoSearch field [find_customer]
idNoOrder ID [get_order]
helpNoReturn the action's full documentation and argument schema instead of running it
pageNoPage number [list_orders, list_customers]
termNoKeyword — searches name / phone / email [list_customers]
limitNoItems per page [list_orders, list_customers]
valueNoSearch value [find_customer]
actionYesWhich operation to run
statusNoFilter by status: 0=new, 1=submitted, 2=shipped, 3=delivered, 4=returning, 5=returned, 6=canceled… [list_orders]

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.8.0

TDQS

A3.8/5.0
Behavior4/5

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

readOnlyHint=true is consistent with everything described, so there is no contradiction risk and the bar is lower. Beyond annotations the description does add value: it discloses that list_orders returns metadata only while get_order returns customer info, items, payment, shipping and discounts, and it documents the help:true probe that returns documentation instead of executing. Pagination, limits and authorization requirements remain undisclosed.

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?

The dispatcher contract is front-loaded in a single sentence, then the four actions are laid out as scannable bullets with no filler. The help:true note is wedged into the opening sentence rather than stated as its own line, which costs a little clarity but not much length.

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?

For a 9-parameter, 4-action tool with no output schema, the definition covers action routing adequately and sketches get_order's return fields. It leaves gaps an agent would care about: what list_orders/list_customers actually return structurally, default and maximum page/limit values, and whether status filtering applies beyond list_orders.

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% and every parameter is already tagged with the action it belongs to ('Order ID [get_order]', 'Search field [find_customer]', 'Filter by status: 0=new, 1=submitted… [list_orders]'), so the schema does the heavy lifting. The description only restates the dispatch pattern ('pick the operation with action and pass that action's arguments') and the help flag, adding little meaning beyond the 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?

The description names the two resources (orders and customers) and then gives each action a distinct verb+resource gloss: 'list_orders: List orders of the site (metadata only)', 'get_order: Get full order details by ID', 'list_customers: List/search the site's customers', 'find_customer: Find a customer by ID, phone number, or email'. That is enough to tell the four actions apart, but it never distinguishes this tool from adjacent siblings such as api_get or product, and bundling orders and customers under the name 'order' slightly blurs the top-level purpose.

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?

The action glosses carry real routing signal: 'metadata only' versus 'full order details by ID' tells an agent which to reach for when browsing versus drilling in, and 'browse or segment' versus 'find by ID, phone number, or email' separates the two customer actions. What is missing is any sequencing advice (list then fetch) or statement of when not to use this tool at all.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.