Skip to main content
Glama

Search Blinkit

blinkit_search

Search Blinkit products at the current delivery location to find items with IDs, pack sizes, prices, MRP, and stock. Use the results to compare options and decide what to add to your cart.

Instructions

Searches Blinkit for a product and returns results with id, pack size, price, MRP and stock, at the current 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": {
      "query": "<query>"
    },
    "name": "blinkit_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many results to return (default 10)
queryYesWhat to search for, e.g. 'amul toned milk'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden; it implies a safe read via 'Searches... returns results' but never says so outright, nor does it mention side effects (there are none obvious) or rate limits. It does add real value by disclosing the location scoping and the exact fields returned, which the schema does not cover.

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?

A single sentence that front-loads the action and then the return shape; nothing is wasted and no clause could be removed without losing information.

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 two-parameter read tool with no annotations and no output schema, the description covers the essentials: what it searches, the location dependency, and the shape of the results. The only gap is the unstated location prerequisite and no mention of how limit interacts with result quality.

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 description coverage is 100%, with both 'query' and 'limit' documented in-schema including a default of 10 and a max of 30, so the baseline is 3. The description adds no syntax, format, or result-count guidance beyond what the schema already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Searches') and resource ('Blinkit for a product'), and enumerates the return payload (id, pack size, price, MRP, stock). It does not explicitly contrast with a sibling, but no sibling competes as a search tool, so disambiguation is effectively achieved by domain.

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

Usage Guidelines3/5

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

The phrase 'at the current delivery location' implies a prerequisite (location must be set, presumably via blinkit_set_location) but never states it or names the alternative. There is no explicit when-to-use/when-not-to-use guidance, leaving the agent to infer that this is the discovery step before add_to_cart.

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