Skip to main content
Glama

Add to cart

blinkit_add_to_cart

Add items to a Blinkit cart with brand, variant, pack size, and optional product IDs; get added and failed items with closest matches plus the updated cart bill.

Instructions

Adds items to the Blinkit cart. Name each item as exactly as you can (brand, variant, pack size) and pass the id from blinkit_search when you have it. Returns what was added, what wasn't and why (with the closest matches), and the cart with its bill.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "items": "<items>"
    },
    "name": "blinkit_add_to_cart"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses that the operation is partial-failure tolerant ('what was added, what wasn't and why') and that near-miss matches are returned, which tells the agent how to recover from naming mismatches. It omits auth/login requirements and whether existing cart contents are preserved, keeping it short of a 5.

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

Conciseness4/5

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

Three sentences, front-loaded with the action, then naming guidance, then return behavior — no filler. The final sentence is slightly dense, packing three distinct outcomes into one clause, but nothing is redundant.

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

Completeness4/5

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

For a cart-mutation tool with no annotations and no output schema, the description covers the two things an agent most needs: how to format item names for reliable matching and what the response contains. Remaining gaps are around authentication state and the effect on pre-existing cart lines, which are minor but real for an unannotated write tool.

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?

The top-level 'items' parameter is undocumented in the schema, and the description compensates by explaining that each item should be named with brand, variant, and pack size, plus the role of the search-supplied id. It adds the rationale (precision improves matching) rather than just restating field names. The nested quantity semantics live in the schema rather than the description.

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 ('Adds items to the Blinkit cart'), which cleanly separates it from blinkit_update_cart, blinkit_view_cart, and blinkit_search by name alone. An agent knows exactly what this call mutates without opening the schema.

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?

Usage is implied through the instruction to pass an id 'from blinkit_search when you have it', which establishes a search-first workflow. However, there is no explicit guidance on when to add versus when to use blinkit_update_cart to change quantities, and no stated prerequisite such as being logged in.

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