muse-commerce-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_catalogA | Search real-time physical retail store inventories near a shopper’s GPS location. Returns verified brick-and-mortar stores, in-stock products, unit prices, and Haversine distance in kilometers. |
| create_orderA | Reserve in-stock items at a local physical store and generate a zero-PII, non-custodial checkout URL. The shopper completes payment and delivery details directly on the verified merchant checkout page. |
| check_order_statusA | Check live fulfillment, payment, and courier dispatch status for an existing local retail order. |
| report_storeA | Submit an autonomous trust-and-safety violation report if a store exhibits deceptive pricing, phantom stock, or invalid coordinates. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: catalog search, order creation, order status lookup, and store reporting. There is no meaningful overlap between discovery, checkout, fulfillment tracking, and trust-and-safety reporting.
All tool names use consistent snake_case and follow a verb-led pattern. The extra noun in check_order_status is still readable and consistent with the domain resource naming.
Four tools are well-scoped for a focused local-commerce workflow. Each tool earns its place and covers a distinct stage without bloat.
The surface covers search, order creation, status checking, and safety reporting, which are the core workflows. Minor gaps exist around order cancellation or listing existing orders, but agents can likely work around them via status checks and merchant checkout.