Skip to main content
Glama
Sign In
agent-browser

agent-browser

by EgiStr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

browser_status

Checks whether Chrome is running, reports headless mode, and lists signed-in Google accounts to verify browser availability and login state.

Instructions

Is the agent Chrome running, headless or not, and which Google accounts are signed in.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full behavioral burden, and it does convey that this is a pure query (phrased as a question about state) reporting headless mode and account sign-ins. It does not disclose whether calling it has side effects such as launching Chrome, or what happens when the browser is not running, though the presence of an output schema covers the return shape.

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 front-loaded sentence that packs three distinct pieces of returned information with zero filler. Every clause earns its place.

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?

For a simple, parameterless read tool with an output schema, the description is nearly sufficient — the agent knows what it will learn. The remaining gap is behavioral: whether it errors, returns running=false, or auto-starts Chrome when no browser exists.

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 there is nothing for the description to disambiguate; the schema is trivially complete. Baseline 4 applies for a no-arg tool.

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 names a specific resource (the agent's Chrome browser) and precisely enumerates the three facts returned: running state, headless mode, and signed-in Google accounts. It is clearly distinguishable from siblings like browser_start/browser_stop. It stops short of explicitly contrasting itself with health_check, the one tool 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?

Usage is only implied: an agent can infer this is a pre-flight check before navigate/login_begin, but the description never says when to call it, when not to, or how it differs from health_check. No exclusions or alternatives are named.

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