Skip to main content
Glama

Live browser link

blinkit_live_view

Open a live Blinkit browser session and share a link so the user can take over to pay, resolve an issue, or watch; starts the browser if needed.

Instructions

A link that shows the Blinkit browser live and lets the person take over: to pay, to solve something, or just to watch. 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_live_view"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose two real behaviors beyond the schema: it hands control to a person, and it starts the browser if it is not already running. It omits link lifetime/expiry, whether the session persists, and what the agent should do after the human takes over — meaningful gaps for a handoff tool.

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 what the result is, then the side effect of launching the browser. Slightly informal wording ("or just to watch", "solve something") costs a bit of precision but no sentence is filler.

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 tool with no output schema, the description usefully conveys that the return value is a link the human opens, plus the auto-start side effect. What is missing is around session lifetime and post-handoff expectations, which an agent coordinating a checkout would want.

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?

There are zero parameters, so there is nothing to disambiguate; baseline 4 applies. The description correctly implies the tool takes no arguments and returns a link rather than requiring any input.

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 states a specific resource (a link to the live Blinkit browser) and what it enables (human takeover to pay, fix an issue, or observe). That is concrete enough to distinguish it from order/cart siblings, though the phrasing is colloquial ("solve something") rather than naming the exact flow it unblocks.

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?

It gives clear usage context by enumerating the three situations that warrant it: paying, resolving a problem, or watching the session. It stops short of explicit exclusions — it never says when to prefer blinkit_checkout or blinkit_submit_otp over handing control to the human — but the intended trigger is unambiguous.

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