Skip to main content
Glama
adrian-baker

woolies-mcp

by adrian-baker

Set several trolley lines at once

set_cart_quantities
Idempotent

Set multiple Woolworths trolley lines in a single call, using absolute quantities (0 removes an item). Each item reports success or failure, including any quantity adjustments applied by the site.

Instructions

Set many products' trolley lines in one call. Quantity is absolute, not a delta: the value you pass becomes the line's new quantity, and 0 removes the line. For pricingUnit, use the product's purchasingUnit field from search_products or get_product verbatim — it is 'Each' or 'Kg'. Only pass 'Kg' with a decimal quantity when the product's canBuyByWeight is true; sending 'Kg' for a counted item orders a kilogram of it. Each item is reported separately as written or failed with a reason; one failure never removes an item from the results, so check every entry. Written entries carry requestedQuantity and appliedQuantity: where adjusted is true the site substituted its own quantity and adjustment says how, so summarise what was actually added. Needs a signed-in session; run npm run login where the server runs, or call sign_in for the details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYesThe lines to set.
Install Server

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that quantity is absolute and 0 removes the line, that results report each item as written or failed, that a failure never drops items from results, and how `adjusted` and `adjustment` fields work. It also warns about the `Kg`/`canBuyByWeight` edge case, which is exactly the behavioral nuance an agent needs.

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?

Every sentence earns its place: the main purpose is front-loaded, then the most important quantity semantics, pricing unit constraints, result handling, adjustment behavior, and auth prerequisite. It is dense but not bloated, with no filler.

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 no output schema, so the description compensates by explaining the per-item result shape, failure semantics, adjustment fields, and auth requirement. It covers enough edge cases that an agent can safely call this mutation tool without further lookups.

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

Parameters5/5

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

Even though the schema already documents `sku`, `quantity`, and `pricingUnit`, the description adds crucial semantics beyond it: absolute-not-delta behavior, 0-removes semantics, using `purchasingUnit` verbatim, and the 'Kg' only-valid-with-`canBuyByWeight` rule. This materially improves correct invocation.

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?

States a specific verb and resource: 'Set many products' trolley lines in one call.' It clearly differentiates from the singular sibling set_cart_quantity by emphasizing batch operation, and the title reinforces 'several trolley lines at once.'

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?

Clearly implies this is for setting multiple cart lines in one call rather than one at a time, and gives important prerequisites like needing a signed-in session and running `npm run login`. It does not explicitly name sibling alternatives or state when not to use it, so it falls just short of full guidance.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/adrian-baker/woolies-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server