blinkit-mcp

Overview Schema Source Related Servers Discussions Admin

blinkit_prepare_order

Prepare an order for payment on Blinkit. Returns a payment token, order ID, and payable amount. Prevents duplicate payment sessions.

Instructions

Mint a payment session for a server-synced cart (createOrder + zomato_payment_hash). Returns PAS token, orderId, payable amount. Fails if the order already has a pending payment.

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": {
      "cart_id": "<cart_id>"
    },
    "name": "blinkit_prepare_order"
  }
}

Input Schema

Name	Required	Description	Default
`cart_id`	Yes	the server cart id (from the web cart / checkout)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 7, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Without annotations, the description carries the full burden. It discloses the creation of an order and payment hash, return values (PAS token, orderId, payable amount), and a failure condition (pending payment). However, it omits details about side effects, permissions, idempotency, or rate limits, which are relevant for a payment-related mutation.

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 concise at two sentences, with the core function front-loaded in the first sentence. Every sentence adds value: the first defines the action, the second details outputs and a failure condition. No redundant information.

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?

Given the tool's simplicity (single parameter, no output schema), the description covers the essential aspects: what it does, what it returns, and a key failure scenario. It is sufficient for an agent to select and invoke the tool correctly, though it could theoretically mention post-usage steps (e.g., using the PAS token).

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 description coverage is 100% for the single parameter 'cart_id', so the baseline is 3. The tool description adds context that the cart_id is 'from the web cart / checkout', which reinforces the schema but does not significantly augment semantic meaning.

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 purpose: 'Mint a payment session for a server-synced cart'. It uses a specific verb ('mint') and resource ('payment session'), and differentiates from siblings by focusing on payment preparation, whereas other tools handle cart manipulation, search, or authentication.

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 provides context by specifying 'for a server-synced cart' and noting that it fails if a pending payment exists. However, it does not explicitly state when to use this tool versus alternatives like blinkit_checkout or blinkit_pay_upi, nor does it offer exclusions or comparative guidance.

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