Skip to main content
Glama
Sign In
agent-browser-mcp

agent-browser-mcp

by zy2755
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

browser_get_info

Retrieve browser health status—mode, open tabs, restart count, and recent errors, dialogs, or downloads—without launching the browser. Diagnose connection and session issues before acting.

Instructions

查询浏览器健康状态:模式、标签列表、重启次数、最近错误/对话框/下载。不会启动浏览器。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the non-obvious side-effect property that it will not launch a browser, plus the diagnostic categories returned. It still leaves open what happens if no session exists (error vs. partial info), which matters for a diagnostic tool.

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?

A single dense sentence front-loads the purpose, then the returned data, then the key safety property. No redundant wording.

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?

No output schema exists, but the description compensates by enumerating the returned fields, and there are no parameters to document. Only the no-session behavior is left unstated, which is a minor gap for a zero-argument diagnostic tool.

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?

The tool takes zero parameters, so the baseline of 4 applies; there is nothing the description needs to disambiguate at the argument level.

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 (query browser health status) and enumerates exactly what is reported: mode, tab list, restart count, recent errors/dialogs/downloads. That distinguishes it from action siblings like browser_click or browser_navigate, though it never names the closely related read siblings (browser_snapshot, browser_tabs) that an agent might confuse it with.

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 clause '不会启动浏览器' implies it is safe to call when no browser is running, which is a real usage signal. However, there is no explicit when-to-use guidance versus browser_snapshot or browser_tabs for inspecting tabs, and no stated preconditions or exclusions.

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