Retrieve live cart state by cart_id: full item list, calculated totals in ZAR, and any customer details stored so far. Call after update_cart to confirm changes are correct before proceeding to create_checkout. Cart expires after 24 hours of inactivity.
| Name | Required | Description | Default |
|---|---|---|---|
| cart_id | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden and does well by disclosing the live nature of the cart, the included data fields, and the 24-hour inactivity expiration. This provides a solid behavioral model, though it does not cover error cases like expired or missing carts.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences: the first states the core function and return contents, the second gives usage context and expiry. Every sentence earns its place, and the key information is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple retrieval tool with one parameter and no output schema, this is complete. It explains what data the agent will receive, when to call it (after update_cart), and what the next step is (create_checkout), plus the cart validity constraint.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema offers only a bare cart_id string with 0% coverage, and the description minimally confirms retrieval by cart_id without adding format or source details. For a single, self-explanatory parameter, this is adequate but not enriching.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Retrieve') and clearly identifies the resource (live cart state by cart_id), listing the exact contents returned (full item list, totals, customer details). This distinguishes it from sibling tools like get_checkout or get_order, which operate on different resources.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly instructs to call this tool after update_cart to confirm changes before proceeding to create_checkout, giving clear workflow sequencing. It does not explicitly mention when-not-to-use or alternative tools, but the contextual guidance is strong.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have distinct purposes, but the presence of three search tools (search_catalog, search_products, lookup_catalog) and legacy tools (create_order, submit_enquiry) creates minor overlap. Descriptions help differentiate, but an agent might initially confuse them.
All 26 tool names follow a consistent verb_noun snake_case pattern (e.g., cancel_cart, configure_product). No mixed cases or irregular verbs are present.
26 tools is slightly high for a blind shop, but the domain requires many operations (search, pricing, cart, checkout, recommendations, etc.). Some legacy tools could be removed, but the count is still reasonable.
The tool surface covers the full customer journey from product discovery (search, recommendations) to purchase (cart, checkout, payment) and post-purchase (orders, swatches, price match, delivery estimates). No obvious gaps for the stated purpose.