Skip to main content
Glama
Browser Control MCP Server

Browser Control MCP Server

by lostmind008

get_current_tab

Retrieves the active Google Chrome tab so AI agents can identify the page currently in focus and target browser actions correctly.

Instructions

Get the active tab in Google Chrome

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": "get_current_tab"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description must carry the full behavioral burden. It conveys only that the operation is a read of the active tab; it says nothing about what the returned tab representation contains (id, url, title), whether it errors when no tab is focused, or whether the call has any side effects such as focusing the page.

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?

A single eleven-word sentence with no filler, and the key noun ('active tab') is front-loaded after the verb. It is efficient but perhaps too terse, leaving out otherwise cheap context such as what the tab object includes.

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

Completeness3/5

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

For a zero-parameter tool this could be near-complete, but with no annotations and no output schema the description is the only source of truth about the return value, and it does not say what 'the active tab' resolves to. Adequate for identifying the call, insufficient for interpreting its result.

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 convey and the baseline of 4 applies. The description neither adds nor omits anything here.

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 verb and resource ('Get the active tab') and pins the environment ('Google Chrome'), so an agent knows it retrieves rather than mutates. It does not, however, distinguish itself from similarly named siblings such as list_tabs or switch_to_tab, leaving the returned object's identity ambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use statement and no mention of alternatives. An agent working in a crowded tab-management space (list_tabs, switch_to_tab, new_tab, close_tab) must infer that this returns the currently focused tab rather than enumerating tabs, with nothing in the definition to confirm that inference.

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