UCP Gateway

shopping cart create

shopping_cart_create

Create a merchant cart after the buyer/operator confirms selected variants.

Input Schema

TableJSON Schema

Name	Required	Description
`buyer`	No	Optional buyer contact summary for cart creation; never include payment data.
`context`	No	Optional buyer/search context for catalog, cart, or checkout tools.
`agent_id`	Yes	Registered UCP Gateway UUID returned by register_ucp_profile; required for every Shopping tool.
`line_items`	Yes	Selected provider variant line items confirmed by the buyer/operator.
`merchant_domain`	Yes	Merchant host such as 'outboundpower.com' or 'example.myshopify.com'. Do not include a URL scheme, localhost, private IP, file URL, or ftp URL.
`client_action_id`	No	Optional UUID generated once for an explicit buyer/operator-confirmed cart or checkout mutation. Reuse only when retrying the same confirmed action.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	True for successful tool execution; false for structured tool errors.
`raw`	No	Redacted raw provider or registry payload for debugging. Shape may vary by upstream endpoint.
`cart`	No	Safe provider cart summary including id, status, continue_url, totals, line_items, and messages when provided.
`error`	No	Structured tool error.
`message`	Yes	Human-readable result summary or recovery message.
`next_step`	Yes	Recommended next step. Suggestions are non-binding and never authorize payment or state-changing actions.
`merchant_domain`	No	Resolved merchant domain.
`commerce_session_id`	No	Internal gateway commerce session UUID when one was created.

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 5, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, and the description consistently labels the operation as 'create'. The description adds the behavioral context of requiring confirmation but does not disclose other traits like idempotency, rate limits, or side effects beyond what annotations provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that conveys the essential purpose and condition. Every word earns its place with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (six parameters, nested objects, output schema), the description is minimal. It adequately covers the core action but lacks mention of prerequisites (e.g., UCP profile registration) or failure conditions. However, with full schema coverage and annotations, it is sufficient for an AI agent.

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 description coverage is 100%, so baseline is 3. The overall description does not provide additional parameter-specific meaning beyond what is already in the schema's descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'create' and resource 'merchant cart'. It distinguishes from sibling cart tools by specifying the condition 'after the buyer/operator confirms selected variants', implying this is for initial creation, not updates or cancellations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear guidance on when to use the tool ('after the buyer/operator confirms selected variants'), but does not explicitly state when not to use it or mention alternative tools like shopping_cart_update.

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

All UCP Gateway tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?