Skip to main content
Glama

browser_capabilities

Reports a browser's input and observation capabilities so agents can verify supported interactions before automating tasks.

Instructions

Report the input and observation capabilities of this browser.

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

Input Schema

NameRequiredDescriptionDefault
browserNoBrowser id from browser_list, or chrome/firefox when only one instance matches.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and does not meet it. 'Report' implies a read, but the description never confirms it is non-mutating, does not say what the response contains, and gives no information on cost, permissions, or 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?

One short, front-loaded sentence with no filler. It is efficient, though the brevity is partly under-specification rather than tight writing.

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?

With no output schema and no annotations, the description should explain what capabilities are reported and in what form. It does neither, so an agent must call it blind to learn the response shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% for the single optional 'browser' parameter, so the baseline of 3 applies. The description adds no meaning beyond the schema, but the schema already documents that the id comes from browser_list or that chrome/firefox suffices with a single instance.

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?

The description has a clear verb ('Report') and scopes it to 'this browser', so it is distinguishable from action-oriented siblings like browser_click or browser_navigate. However, 'input and observation capabilities' is left undefined, so an agent cannot tell concretely what is being reported (supported input methods? observable event types?).

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 guidance on when to call this versus alternatives such as browser_list, browser_observe, or browser_events. No prerequisites or exclusion conditions are stated.

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