Skip to main content
Glama

Blinkit status

blinkit_status

Checks Blinkit login state, delivery location and time, and cart item count, starting the browser if needed.

Instructions

Whether the Blinkit browser is logged in, the delivery location it is set to, the delivery time shown, and how many items are in the cart. Starts the browser if it isn't running.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "blinkit_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/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 it delivers the single most important non-obvious behavioral fact: the call starts the browser if it is not running. That is a real side effect an agent must know before invoking. It stops short of describing latency, whether a login attempt is triggered, or what happens if the browser fails to start.

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?

Two short sentences, front-loaded with the returned information and closing with the side-effect caveat. The list of fields is dense but each item is meaningful; only the slightly awkward phrasing 'the delivery location it is set to' could be tightened.

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?

There is no output schema, so the description must communicate what comes back, and it does so by naming the four status fields. It omits the return format (flat object vs nested) and any failure modes, which are minor gaps for a zero-argument status probe but not negligible.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description does not waste space on arguments and instead spends its words on the returned status fields.

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?

The description names a specific resource (Blinkit browser status) and enumerates exactly what is reported: login state, delivery location, delivery time, and cart item count. This distinguishes it from siblings like blinkit_view_cart and blinkit_addresses, which return a subset of this information, though it does not name any sibling explicitly.

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?

Usage is only implied: an agent can infer this is the tool to call to check overall session state before acting. There is no explicit when-to-use guidance, no exclusions, and no statement of how it relates to blinkit_login, blinkit_view_cart, or blinkit_addresses, so the agent must reason about selection itself.

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