Skip to main content
Glama
Sign In
browser-use-native-windows

browser-use-native-windows

by mlnima
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Observe Browser

browser_observe

Launch or adopt a Windows browser, optionally navigate to a URL, and return an observation of the browser window or file dialog.

Instructions

Launch or adopt a Windows browser, optionally handle a target URL through native UI, and return a browser-window or browser-owned file-dialog observation.

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

Input Schema

NameRequiredDescriptionDefault
targetUrlNo
inlineImageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description must fully disclose behavioral traits. It mentions launch/adopt and URL handling but lacks details on side effects (e.g., whether it opens a new window, modifies browser state), auth requirements, or blocking behavior. The phrase 'native UI' is vague.

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 description is a single sentence that conveys multiple aspects (launch/adopt, optional URL, return type). It is reasonably concise, though slightly long. No redundancy.

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?

Given the absence of an output schema, the description should clarify the return format. It only says 'return a browser-window or browser-owned file-dialog observation,' which is too vague. Parameter explanations are missing, leaving the agent with insufficient context.

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%, so the description must compensate. It only hints at 'targetUrl' ('optionally handle a target URL') but does not name or explain either parameter, and 'inlineImage' is entirely absent. This adds minimal value over the raw schema.

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?

The description clearly states the verb ('launch or adopt'), resource ('Windows browser'), and the outcome ('return a browser-window or browser-owned file-dialog observation'). It distinguishes from sibling tools like browser_act and browser_stop by focusing on observation.

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?

The description provides no guidance on when to use this tool vs alternatives (siblings are browser_act, browser_status, browser_stop). There is no mention of prerequisites, limitations, or when not to use it.

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