Skip to main content
Glama

browser_status

Read-onlyIdempotent

Check whether the opt-in Playwright browser configuration is enabled before running browser tests.

Instructions

Check the opt-in Playwright browser configuration.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, non-destructive, idempotent, closed-world), so the description's main added value is the "opt-in" signal that browser functionality is gated by configuration. It stops short of describing what the check returns, what happens when the browser is not configured, or whether calling it has any side effects.

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, appropriately sized for a zero-parameter status tool. It is slightly ambiguous in that "check the configuration" reads more like validating than reporting status.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description is the only place an agent can learn what this returns, and it does not say (configuration flags, enabled/disabled, readiness). For a simple read-only status tool the gap is tolerable, but it leaves the agent guessing about the payload.

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 and the baseline for a parameterless tool applies. No parameter-level gaps exist.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Check the opt-in Playwright browser configuration" gives a verb (check) and a resource (browser configuration), but it is close to a restatement of the name and never says what a "status" actually reports. It also does not distinguish this from nearby siblings such as browser_diagnostics, which an agent could plausibly pick instead.

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?

There is no when-to-use guidance: nothing says whether to call this before browser_open, when a browser operation fails, or how it differs from browser_diagnostics. The word "opt-in" hints that browser tooling must be enabled, but the implication is never stated as an actionable precondition.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.