Skip to main content
Glama

Change cart

blinkit_update_cart

Update item quantities, remove products, or empty the Blinkit cart in one request; set quantity to 0 to delete an item.

Instructions

Changes quantities in the Blinkit cart, removes items, or empties it. Quantity 0 removes an item.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "blinkit_update_cart"
  }
}

Input Schema

NameRequiredDescriptionDefault
clearNoRemove everything from the cart
changesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it does disclose the key semantics that quantity 0 removes an item and that the cart can be emptied outright. It says nothing about authentication/login requirements, whether quantities replace or are additive to the existing value, precedence when both fields are supplied, or what a successful call returns.

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?

Two short sentences, operation list front-loaded, and the non-obvious 0-equals-remove rule immediately follows. No filler or 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?

For a two-parameter mutation tool with no annotations and no output schema, the description covers the operations but not the operational context: required login state, whether existing cart contents are fetched first, mutual exclusivity of `clear` vs `changes`, or how failures (item not in cart) surface.

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 coverage is 50% (the `changes` array itself is undocumented), and the description's content — quantity 0 removes an item, emptying the cart — largely restates what the schema already says for `quantity` and `clear`. It adds no format, ordering, or interaction semantics beyond the structured fields.

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

Purpose4/5

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

States a specific verb set (change quantities, remove items, empty) against a named resource (the Blinkit cart), which makes it obviously distinct from blinkit_add_to_cart and blinkit_view_cart. It does not explicitly name those siblings, so the differentiation is inferable rather than stated.

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

Usage Guidelines3/5

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

The three operations imply when to reach for this tool (adjust quantity, delete a line item, wipe the cart), but there is no explicit when-to-use/when-not guidance and no named alternative for adding new items. It also leaves open whether `clear` and `changes` may be combined in one call.

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