blinkit-mcp

by yniks

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

blinkit_send_otp

Sends a one-time password to a 10-digit Indian mobile number to initiate login on Blinkit.

Instructions

Send a login OTP to a phone number (headless, no browser). Step 1 of login.

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": {
      "phone": "<phone>"
    },
    "name": "blinkit_send_otp"
  }
}

Input Schema

Name	Required	Description	Default
`phone`	Yes	10-digit Indian mobile number, e.g. 9876543210

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 7, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, description carries full burden. It mentions headless execution but does not disclose side effects (e.g., SMS sending, rate limits) or whether login state changes. Adequate but lacks depth.

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?

Single sentence, no redundancy, essential information front-loaded.

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 1-parameter tool with no output schema, description is adequate. Mentions step 1 of login, providing sequencing context. Could briefly hint at next step (verify OTP).

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 already covers the phone parameter with format example. Description does not add new meaning beyond 'phone number'. Schema coverage is 100%, so baseline score applies.

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?

Description clearly states the tool sends a login OTP to a phone number, specifying it is headless and step 1 of login. This distinguishes it from sibling tools like 'blinkit_verify_otp'.

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?

Explicitly identifies it as step 1 of login, implying usage before verification tools. However, does not mention scenarios where it should not be used (e.g., if already logged in).

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