MCP tool reference
Discover the current schemas and use the implemented tool groups.
After connecting, use the SDK's tools/list operation. Its schemas are the authoritative contract for that server version. Implementations are registered by apps/platform/src/mcp/server.ts; aa_ compatibility aliases retain the same checks where installed.
First read calls
| Tool | Inputs | Purpose |
|---|---|---|
m0_list_merchants | limit, optional cursor | Browse published profiles |
m0_get_merchant_profile | slug | Read a profile and its merchant identifier |
m0_search_products | query, optional merchantId | Search visible catalog products |
m0_discover_merchant | merchantDomain | Discover merchant capabilities |
m0_query_metrics | range; merchantId when needed | Read your storefront's traffic metrics |
m0_get_analytics_report | Inspect the returned schema | Read a named traffic report |
After selecting a listed slug, use m0_get_merchant_profile to obtain the merchantId for product search. Do not derive it from a display name.
Commerce
Cart tools: m0_create_cart, m0_get_cart, m0_update_cart, m0_cancel_cart.
Checkout tools: m0_create_checkout, m0_get_checkout, m0_update_checkout, m0_complete_checkout, m0_cancel_checkout.
Inspect the schema first. Store capabilities, account environment, scopes and checkout rail determine availability. Completion still enforces authority, payment and owner-confirmation requirements.
Other groups
Agent, wallet, card, mandate, policy, user, authority and analytics tools also exist in source. Code capability is not a promise that every account has every feature or every payment rail enabled. Discover tools rather than hardcoding a count.
Check isError, preserve non-secret request/session identifiers, and retry only transient errors. Never replay a financial operation without its required idempotency semantics.