blinkit-mcp

by yniks

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

blinkit_recommendations

Retrieve products frequently bought with a specified product ID for cross-selling recommendations.

Instructions

Products frequently bought with a given product id ('people also bought').

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": {
      "product_id": "<product_id>"
    },
    "name": "blinkit_recommendations"
  }
}

Input Schema

Name	Required	Description	Default
`product_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 7, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations provided, so the description must disclose behavioral traits. It only states the purpose but does not clarify whether the tool is read-only, has side effects, or requires authentication. The agent cannot infer safety or idempotency from this description.

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?

Single sentence that is front-loaded and concise. No wasted words, but could include more detail without being verbose.

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

Completeness2/5

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

The tool is simple with 1 parameter and no output schema. The description does not specify the return format (e.g., list of product IDs or objects) or whether it includes pricing/availability. This leaves the agent guessing the response structure.

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 0%, so the description must add meaning. It mentions 'given product id' which adds context but no extra constraints (e.g., format, range). For a single integer parameter, this is acceptable but could be more helpful (e.g., 'must be a valid product ID from blinkit catalog').

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?

Clearly states it returns products frequently bought with a given product ID ('people also bought'). The verb 'recommends' and resource 'products' are specific, and the description distinguishes it from sibling tools like search or cart operations.

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?

Implied usage: when a user wants to see 'people also bought' recommendations for a product. However, no explicit guidance on when to use vs. alternatives (e.g., search, home feed), and no exclusions or prerequisites mentioned.

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