Skip to main content
Glama
Sign In
omni-browser

omni-browser

by rianprei
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

browser_snapshot

Reads accessibility-oriented page structure, letting MCP clients inspect page content without requiring a screenshot.

Instructions

Read accessibility-oriented page structure (no screenshot required).

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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; 'Read' implies a non-destructive operation and 'no screenshot required' tells the agent it is cheap/structural rather than visual, which is useful context. It does not disclose what the structure contains (roles, names, element references usable by browser_click) or whether it changes page state.

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 front-loaded sentence with no filler; the key noun phrase comes first. It is efficient, though its brevity is close to under-specification rather than true economy.

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

Completeness2/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 does not describe the shape of the returned structure or how the limit affects it. For a snapshot tool whose output the agent must interpret, that leaves a material gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single 'limit' parameter, and the description never mentions it, so the agent gets no information about what the limit counts (elements? depth? characters?) or its default. The description fails to compensate for the schema gap.

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?

States a specific verb and resource: 'Read accessibility-oriented page structure,' and the parenthetical 'no screenshot required' implicitly contrasts it with browser_screenshot. It is less clear how it differs from the sibling browser_read, which keeps it from a 5.

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?

The parenthetical hints at when to prefer this over a screenshot, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative. Usage is only implied.

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