Skip to main content
Glama
Sign In
self-healing-browser-mcp

self-healing-browser-mcp

by RAJUSHANIGARAPU
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

browser_snapshot

Retrieve a semantic view of a web page by listing interactive elements with roles and accessible names, enabling informed decisions for automation actions.

Instructions

Return the page's interactive elements as roles + accessible names.

Use this to 'see' the page semantically before deciding what to click or type.

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

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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. It implies a read-only operation ('return', 'see'), but does not explicitly state safety, side effects, or performance. Basic transparency is present, but deeper behavioral details are missing.

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?

Two sentences, front-loaded with the core action, and a usage hint. No extraneous words; every sentence serves a purpose.

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?

Given zero parameters and an output schema, the description covers the essential aspects: what it returns and why to use it. Minor missing details could include whether it captures the full page or visible viewport.

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?

No parameters exist, so schema coverage is 100%. The description adds value by explaining the output nature (roles and accessible names), going beyond the minimal schema. Baseline 4 is appropriate.

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 clearly states it returns interactive elements as roles and accessible names, with a usage hint. It distinguishes from siblings like browser_click and browser_fill by focusing on semantic introspection, but does not explicitly contrast with browser_get_text.

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 description includes 'Use this to see the page semantically before deciding what to click or type', providing a clear context. However, it does not specify when not to use it or mention alternatives like browser_get_text for text extraction.

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