Skip to main content
Glama

Log in (send OTP)

blinkit_login

Start a Blinkit login by sending a one-time code to a mobile number, then verify it to access the account. Needed only once, since the login is remembered.

Instructions

Starts a Blinkit login with a mobile number: Blinkit texts that number a one-time code. Follow with blinkit_submit_otp. Only needed once; the login is remembered. Blinkit signs up a number it doesn't know, under its terms, so use this only for the number's owner at their request.

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

Input Schema

NameRequiredDescriptionDefault
phoneYesTheir 10-digit Indian mobile number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations exist, so the description carries the full load, and it does disclose non-obvious behavior: an SMS is dispatched, the session persists across calls, and an unknown number is silently signed up under Blinkit's terms. It stops short of disclosing rate limits, OTP expiry, or what happens if a session already exists.

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 short sentences, front-loaded with the action and its effect, then the follow-up step, then the consent caveat. The final clause about signup terms is slightly long but carries real policy weight rather than filler.

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 one-parameter auth entry point with no output schema, the description covers the trigger, the side effect, the persistence, and the consent constraint. The one omission is what the call yields (e.g., a request identifier or session marker) needed to reason about calling submit_otp, though the sibling reference mitigates this.

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 100% and the single parameter is fully described there, including the Indian-mobile pattern, so the baseline applies. The description only confirms the number is the SMS target and adds nothing about format or normalization beyond the 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?

States a specific verb and resource ('Starts a Blinkit login with a mobile number') plus the concrete side effect ('Blinkit texts that number a one-time code'). It also names the exact sibling to call next (blinkit_submit_otp), so an agent can place it in the auth flow without opening other schemas.

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

Usage Guidelines5/5

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

Gives the sequencing rule ('Follow with blinkit_submit_otp'), a reuse condition ('Only needed once; the login is remembered'), and an explicit restriction ('use this only for the number's owner at their request'). Both when-to-use and when-not-to-use are covered.

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