NEVINI Wines

Add to cart

add_to_cart

Adds wine variants to an existing cart; quantities add up with lines already in the cart. Returns the updated cart and checkout_url. No order is placed and no payment is taken here; checkout_url opens the checkout on shop.nevini.wine. Use create_cart when there is no cart yet and update_cart to change or remove lines already in the cart.

Input Schema

Name	Required	Description
`items`	Yes	Wines to add. Duplicate variant ids are merged; a cart holds at most 25 different variants.
`cart_id`	Yes	cart_id exactly as returned by create_cart, including its ?key= part.
`language`	No	Language of item names and of the checkout: "nl" (default) or "en".

Output Schema

Name	Required	Description	Default
`items`	Yes
`cart_id`	Yes
`currency`	Yes
`warnings`	Yes
`next_step`	Yes
`checkout_url`	Yes
`order_placed`	Yes
`subtotal_eur`	Yes
`shipping_note`	Yes
`total_quantity`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 26, 2026

removedOutput schema / properties / age_notice
```
Removed value: -{
-  "type": "string"
-}
```

changedOutput schema / required

Previous value: -[
-  "cart_id",
-  "order_placed",
-  "currency",
-  "items",
-  "total_quantity",
-  "subtotal_eur",
-  "checkout_url",
-  "next_step",
-  "age_notice",
-  "shipping_note",
-  "warnings"
-]New value: +[
+  "cart_id",
+  "order_placed",
+  "currency",
+  "items",
+  "total_quantity",
+  "subtotal_eur",
+  "checkout_url",
+  "next_step",
+  "shipping_note",
+  "warnings"
+]

First observedOct 25, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations establish that this is a non-read-only, non-destructive, non-idempotent mutation. The description adds important behavior beyond annotations: quantities accumulate with existing cart lines, no order or payment occurs, and checkout_url is returned for external checkout.

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 front-loaded with the core action and scope, then immediately covers return behavior, side effects, and alternatives. Every sentence contributes useful selection or invocation information.

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

Completeness5/5

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

The tool has rich schema coverage, annotations, and an output schema, and the description still covers the critical behavioral context: cart existence, additive quantities, no payment/order, and checkout URL. Nothing essential for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is already strong. The description adds meaningful semantics for the quantity parameter by explaining that quantities add to existing cart lines rather than replacing them.

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 states a specific verb and resource: adding wine variants to an existing cart. It also distinguishes the tool from create_cart and update_cart, so an agent can select it without opening sibling schemas.

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

Usage Guidelines5/5

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

It explicitly says to use create_cart when no cart exists and update_cart to change or remove existing lines. This gives clear when-to-use and when-not-to-use guidance with named alternatives.

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

All NEVINI Wines 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?