blinkit-mcp

by yniks

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

blinkit_view_cart

Retrieve your current cart details including repriced items, payable amount, delivery charge, and minimum order value.

Instructions

Show the working cart, repriced (items, payable amount, delivery, MROV).

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_view_cart"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 7, 2026

TDQS

A3.8/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only says 'Show', implying read-only, but does not explicitly state it is non-destructive, idempotent, or requires authentication. No side-effects or permissions are addressed.

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 concise sentence that front-loads the action ('Show the working cart, repriced') and lists key output elements. No wasted words.

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 simple view-only tool with no parameters, the description provides essential information about the tool's purpose and output. It could mention that the tool is safe and read-only, but overall it is fairly complete.

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 input schema has no parameters, so description coverage is 100%. The description adds meaning by listing what is shown (items, payable amount, delivery, MROV), which is useful for understanding the output without an output schema.

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 tool's function: showing the working cart with updated pricing, including items, payable amount, delivery, and MROV. It distinguishes from sibling tools like blinkit_add_to_cart and blinkit_clear_cart which modify the cart.

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 description implies use for viewing the cart but does not explicitly state when to use it vs alternatives like blinkit_checkout or blinkit_prepare_order. No exclusions or prerequisites are mentioned.

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