CartClaw
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CARTCLAW_BROWSER | No | Browser path | |
| CARTCLAW_PROFILE | No | Profile folder | ~/.cartclaw/profile |
| CARTCLAW_CDP_PORT | No | CDP port (default 9333) | 9333 |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ordersA | Order history with each item's return window. period: 'last30', 'months-3' or 'year-YYYY'. Amazon shows 10 orders per page; max_pages caps how many pages are read. |
| returnable_itemsA | Items from the last 3 months whose return window is still open, soonest deadline first. |
| productA | Title, price and availability for one product by ASIN (e.g. from orders). |
| cartA | What is in the cart now, with the subtotal. |
| cart_addB | Add a product to the cart (one-time purchase, not Subscribe & Save). Returns the cart. |
| cart_removeB | Remove a product from the cart. Returns the cart. |
| checkout_requestA | Ask the user to approve buying the current cart. Opens Amazon's checkout review (nothing is placed), then an approval page in the user's browser showing total, items, address and card. Returns at once with status 'pending'; poll checkout_status. The user can approve or decline. |
| checkout_statusA | Where an approval stands: pending, switching (the user is changing the card), placing, placed (with order_number), rejected, expired, superseded or failed (with detail). |
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 8 tools
Each tool has a distinct purpose: orders (history) vs returnable_items (open-window filter), product (lookup), cart/cart_add/cart_remove (view/add/remove), and checkout_request vs checkout_status (initiate vs poll). No two tools overlap in a way that would cause misselection.
Mostly noun-based names with clear grouping: cart_ prefix for cart mutations and checkout_ prefix for the two-phase approval flow. Minor inconsistency in that orders is plural while product and cart are singular, but the convention is readable and predictable.
Eight tools is well-scoped for a shopping/checkout assistant, covering the full browse-to-purchase flow without redundancy. Every tool earns its place.
Core lifecycle is covered: order history, returns, product info, full cart CRUD, and a two-phase checkout with status polling. Minor gaps exist (no product search beyond ASIN, no cart quantity update), but agents can work around these via existing tools.