Skip to main content
Glama

Close the browser

blinkit_close

Closes the Blinkit browser session while keeping the login, so the next tool call opens a fresh browser.

Instructions

Stops the Blinkit browser session (it stops by itself after 10 idle minutes). The login is kept; the next tool call starts a new browser.

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_close"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 meaningful work: it discloses that the login persists and that the next tool call cold-starts a browser, which is exactly the consequence an agent needs to know before interrupting a flow. It omits whether in-flight operations are aborted and what happens if no session exists (no-op vs error), leaving a real 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 short clauses, both load-bearing: the first identifies the action, the second carries the two behavioral facts (idle auto-stop, login retained). No filler or restatement of the title.

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 zero-parameter teardown tool with no output schema, this is nearly complete — cost of calling, side effect on the session, and the follow-on state are all covered. Only failure semantics (calling when no browser is running) are missing.

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 meaning to add; the baseline for a 0-param schema is 4. Nothing in the description is needed to clarify inputs.

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 ('Stops') and a specific resource ('the Blinkit browser session'), so it is immediately distinguishable from session-lifecycle siblings such as blinkit_login or blinkit_status. No ambiguity about what the call does.

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?

The parenthetical 'it stops by itself after 10 idle minutes' implicitly tells the agent this call is optional and only needed to force an early shutdown; that is strong usage context. It stops short of naming an explicit alternative or spelling out when-not to call (e.g., mid-checkout), so not a 5.

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