Skip to main content
Glama

Log in (enter OTP)

blinkit_submit_otp

Submit the SMS one-time code to finish a Blinkit login and unlock browsing, cart, and bill review in the same session. The code and login page expire quickly, so send it right after it arrives.

Instructions

Finishes the login started by blinkit_login, with the one-time code Blinkit texted. Call it soon after: the code and the page both expire.

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": {
      "otp": "<otp>"
    },
    "name": "blinkit_submit_otp"
  }
}

Input Schema

NameRequiredDescriptionDefault
otpYesThe code from the SMS

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it usefully discloses the expiry of both the OTP and the underlying page session, which is genuine behavioral context beyond the schema. It does not say what happens on an incorrect or expired code (error shape, retry limits) or whether a successful call establishes a persistent session.

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?

Two compact sentences, front-loaded with the action and its prerequisite, with the expiry caveat in second position. No filler.

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

Completeness3/5

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

For a one-parameter authentication step this covers the essentials of when and what, but with no annotations and no output schema nothing describes the post-success state (logged in?) or failure modes. Adequate, not complete.

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 otp parameter is documented with a digit pattern, so the description need only confirm what the code is. It does so ('the one-time code Blinkit texted') but adds no format or sourcing detail beyond the schema's 'The code from the SMS'.

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 action (finishing a login with a one-time code) and explicitly ties it to the sibling tool blinkit_login that starts the flow. An agent can distinguish this OTP-submission step from blinkit_login without opening either schema.

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?

Gives clear context: it must be called after blinkit_login and 'soon after,' because both the code and the page expire. It doesn't name a fallback for an expired code (e.g. re-run blinkit_login), but the sequencing guidance is explicit.

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