Skip to main content
Glama

Set delivery location

blinkit_set_location

Sets a Blinkit delivery location by area, address, or pincode before product searches, ensuring prices, stock, and delivery times match the chosen destination.

Instructions

Sets where Blinkit delivers to, by area, address or pincode (e.g. 'Indiranagar, Bengaluru'). Prices, stock and delivery time depend on it, so set it before searching. It picks Blinkit's best match and lists the other matches.

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

Input Schema

NameRequiredDescriptionDefault
locationYesArea, address or pincode

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does real work: it discloses the downstream effects (prices, stock, delivery time) and the resolution behavior (picks Blinkit's best match and lists the other matches), effectively describing the return payload despite no output schema. It does not mention auth/prerequisite state or what happens when nothing matches, which is a modest gap.

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 sentences, no filler, and the ordering constraint is front-loaded where the agent will read it first. Every clause contributes either scope, prerequisite, or behavior.

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 single-parameter tool this covers purpose, prerequisite ordering, and resolution/return behavior well. The only omissions are failure handling when no location matches and any login/session prerequisite, which are minor for this complexity level.

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

Parameters4/5

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

Schema coverage is already 100%, so the baseline is 3; the description adds value beyond the schema by giving an example format ("Indiranagar, Bengaluru") that clarifies what a valid location string looks like. It does not elaborate on ambiguity handling for the single parameter, so it does not reach 5.

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 ("Sets where Blinkit delivers to") and enumerates the accepted input forms (area, address or pincode) with an example. No sibling tool in the list performs this action, so the agent can distinguish it immediately.

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 explicit ordering guidance: prices, stock and delivery time depend on it, so it must be set before searching. That is a clear when-to-use condition. It stops short of naming an alternative (e.g. blinkit_addresses) or stating when-not to use it, which keeps it out of 5 territory.

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