Skip to main content
Glama
Sign In
chrome-fast

chrome-fast

by ventos312
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_page

Read-only

Retrieve the current Chrome page content as an accessibility tree with numbered element references for clicking or typing, a compact interactive view, or raw HTML.

Instructions

Get the current page content. The default is an accessibility tree with the page text and numbered element refs you can pass to click/type; "interactive" leaves out the text lines for a compact view; "html" returns the raw HTML.

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

Input Schema

NameRequiredDescriptionDefault
formatNoOutput format (default: accessibility)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish that this is read-only. The description adds useful behavioral detail about what each output contains, including numbered element refs and the compact interactive view, though it does not discuss limits or page-state requirements.

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?

The description is front-loaded with the core action and then cleanly explains the three output modes with no wasted wording.

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?

For a simple one-parameter read tool with annotations and no output schema, the description is complete: it explains the default behavior and distinguishes all three output formats an agent might request.

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% and the enum values are already listed. The description meaningfully explains what each enum value returns: accessibility tree with text and refs, compact interactive view without text lines, and raw HTML.

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 current page content.' It is clearly distinct from navigation, screenshot, and evaluation tools, but it does not explicitly contrast itself with those siblings.

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

Usage Guidelines3/5

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

It explains the format options and implies that the default accessibility output is useful for click/type interactions, but it does not explicitly say when to use this tool instead of screenshot, evaluate, or navigate.

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

Deploy Server

Other Tools