blinkit-mcp

Overview Schema Source Related Servers Discussions Admin

blinkit_set_location

Set delivery location by providing latitude and longitude. Confirms serviceability and selects the nearest express dark store as the default.

Instructions

Resolve a lat/lon, confirm serviceability, pick the express dark store, and save it as the default delivery location.

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": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "blinkit_set_location"
  }
}

Input Schema

Name	Required	Description	Default
`lat`	Yes
`lon`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 7, 2026

TDQS

B3.3/5.0

Behavior3/5

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

No annotations exist, so description bears full burden. It mentions the side effect of saving a default location, but lacks details on error behavior, idempotency, or failure modes (e.g., invalid coordinates).

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?

The description is a single sentence with minimal words, but it crams multiple sequential actions into one clause, reducing readability. Could benefit from bullet points or separate sentences.

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?

No output schema and no annotations, yet the description covers the core functionality. However, it omits return values, error states, and important behavioral nuances for a setup tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description should elaborate on parameters, but only references 'lat/lon' without specifying format, range, or precision. The schema names are insufficient.

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 outlines a sequence of actions: resolve lat/lon, confirm serviceability, express dark store selection, and save as default. It uses specific verbs and distinguishes from siblings like blinkit_check_serviceability.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives (e.g., blinkit_check_serviceability) or prerequisites (e.g., login status). The description lacks context for appropriate invocation.

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