Skip to main content
Glama

tab_read

Read the current browser page as a compact outline of headings, visible text, and interactive controls with refs for clicking, typing, or filling forms.

Instructions

Read a page in the user's own browser as a compact outline instead of HTML: headings, visible text, and every visible control on its own line with a ref, role, name and state, e.g. [12] textbox "Email" value="" required or [13] button "Sign in". Open dialogs come first. Pass those refs to tab_click, tab_type, tab_fill, tab_select_option and tab_scroll; to find one control on a long page, tab_find is cheaper. Reading does not move the mouse or switch tabs. Defaults to what is on screen in the active tab; use scope "page" for the whole page, and tab_screenshot when the look of the page matters, or when the outline leaves you unsure what the user sees (a dialog, a canvas, a page that changed unexpectedly).

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

Input Schema

NameRequiredDescriptionDefault
refNoRead only one part of the page, whole: the ref of a heading reads the section it titles, the ref of a dialog the dialog, the ref of a control what is inside it. Ignores scope.
scopeNoviewport reads only what is on screen now, as the user sees it; page reads the whole page. Defaults to viewport.
tabIdNoTab id from tab_list or tab_read. Defaults to the active tab of the browser window the user used last.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description does real work: it declares the operation is non-disruptive ('Reading does not move the mouse or switch tabs'), discloses ordering of results ('Open dialogs come first'), and states the default target ('what is on screen in the active tab'). It does not mention truncation/size limits on very long pages or error behavior, so it stops short of a 5.

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?

The core definition is front-loaded and the inline examples ('[12] textbox "Email" value="" required') convey the format faster than prose would. The single dense paragraph packs several distinct ideas, but nearly every clause carries actionable information.

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

Completeness5/5

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

There is no output schema, and the description compensates by describing return content, ordering and concrete formatting examples. Combined with the default behavior, scope override, and cross-tool ref chaining, an agent has everything needed to invoke it correctly.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by explaining that refs produced here are the inputs to the click/type/fill/select/scroll tools and that tabId originates from tab_list or tab_read. The ref/scope interaction is largely mirrored from the schema, which keeps it from a 5.

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 and resource ('Read a page in the user's own browser') plus the exact output shape ('compact outline instead of HTML'), which immediately separates it from tab_screenshot and the interaction tools. The enumeration of headings/text/controls with refs, role, name and state makes the tool's identity unambiguous.

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

Usage Guidelines5/5

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

Explicitly routes downstream usage ('Pass those refs to tab_click, tab_type, tab_fill, tab_select_option and tab_scroll'), names the cheaper alternative for a narrower task ('to find one control on a long page, tab_find is cheaper'), and gives the condition that selects tab_screenshot. It also states the scope choice ('use scope "page" for the whole page').

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