Skip to main content
Glama
Sign In
apparelhub-mcp

apparelhub-mcp

Official
by ApparelHub-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_my_orders

Read-only

List recent merchant orders across channels, filter by fulfillment source (merchant or ApparelHub), and surface orders requiring attention with actionable messages.

Instructions

List the merchant's recent orders across channels. An order with fulfilled_by: 'merchant' is for the merchant's own products (brought in from their sales channel, not made in ApparelHub): their store fulfils it, ApparelHub only records it, and approve / submit / confirm / cancel / hold / record-payment refuse it with fulfilled_by_merchant; tell the user to act on it in their store. Pass fulfilled_by to list only those ('merchant') or only ApparelHub-fulfilled orders ('apparelhub'). An order carrying needs_attention is one the merchant must act on (the fulfillment provider failed or cancelled it, the buyer cancelled after production started, it was paid but never sent to production, the sales channel's ship-by deadline is close or missed, or the channel refused the tracking): always tell the user about those, with the message. ship_by_at is the channel's ship-by deadline (UTC) when it has one. Read-only.

[#fc1938]

Input Schema

NameRequiredDescriptionDefault
limitNo
sinceNoISO date lower bound where supported.
statusNo
workspaceNo
store_uuidNo
fulfilled_byNo'merchant' = orders for the merchant's own products, fulfilled by their store; 'apparelhub' = orders ApparelHub fulfils. Omit for both.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.19.0
    • addedInput schema / properties / fulfilled_by
      Added value: +{
+  "description": "'merchant' = orders for the merchant's own products, fulfilled by their store; 'apparelhub' = orders ApparelHub fulfils. Omit for both.",
+  "enum": [
+    "merchant",
+    "apparelhub"
+  ],
+  "type": "string"
+}
  2. First observedv0.15.2

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses important behavioral context: merchant-fulfilled orders cannot be acted on via approve/submit/confirm/cancel/hold/record-payment, how needs_attention should be surfaced, and what ship_by_at means.

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 description is front-loaded with the core action and then supplies dense operational context. It is longer than typical, and the trailing '[#fc1938]' artifact is extraneous, but most sentences carry useful information.

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 read-only list tool with no output schema, it explains key result fields such as needs_attention and ship_by_at and gives handling guidance. It remains incomplete on several input parameters and does not discuss pagination behavior.

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 coverage is only 33%, and the description adds meaningful context for fulfilled_by but does not explain limit, status, workspace, or store_uuid. It therefore partially compensates for the schema gap rather than fully documenting parameter semantics.

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 states a clear verb and resource: 'List the merchant's recent orders across channels.' This lets an agent distinguish it from detail or summary siblings, though it does not explicitly name an alternative tool.

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?

It explains how to use the fulfilled_by filter and how to handle merchant-fulfilled and needs_attention orders, but it does not state when to choose this tool over alternatives such as get_order_details, get_orders_summary, or list_pending_fulfillments.

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

Deploy Server

Other Tools