Skip to main content
Glama

request_bypass

Request temporary access to every open browser tab instead of only shared ones. Prompts the user with your reason and waits for approval, so use it only when a task needs other tabs.

Instructions

Ask the user for bypass mode, which gives you every open tab in the browser instead of only the shared ones. The browser shows the user a prompt with your reason and waits up to two minutes for an answer. Only ask when the task needs other tabs.

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": {
      "reason": "<reason>"
    },
    "name": "request_bypass"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYesOne sentence the user will read, saying why you need the other tabs.
browserNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the whole burden, and it does surface real behavior: a user-facing prompt containing the supplied reason and a wait of up to two minutes. It does not say what the agent gets back if the user declines or the prompt times out, nor whether the grant persists for the session. Useful but incomplete for a consent-gated 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?

Three short sentences with the capability stated first, the user-facing consequence second, and the usage restriction last. No filler, though the warning about sparing use could be merged for tightness.

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 consent tool with no output schema, the description covers purpose, the user-visible prompt, the timeout, and the usage gate, which is most of what an agent needs. The missing pieces are the undocumented 'browser' parameter and the outcome of a denied or timed-out request.

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?

The schema already describes 'reason' in detail, and the description only reinforces that it is shown to the user. The second parameter, 'browser', is documented in neither the schema nor the description, leaving one of two parameters semantically opaque at 50% coverage.

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 concrete action (ask the user for bypass mode) and immediately explains its effect: access to every open tab rather than only shared ones. That scope distinction is what an agent needs to tell this apart from plain tab-listing tools. It stops short of 5 only because 'bypass mode' is tool-specific jargon that is defined only by the following clause.

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?

Explicitly gates usage: 'Only ask when the task needs other tabs,' which tells the agent not to spend a user prompt on routine work that the shared-tab tools cover. No alternative tool is named, but the condition for use is unambiguous.

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