Skip to main content
Glama

browser_events

Retrieves recent human-takeover events from the last ten minutes (up to 100) so agents can detect when a user intervenes in browser control. No page contents are recorded.

Instructions

Read recent human-takeover events (last ten minutes, up to 100). No page contents are recorded.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure, and it does provide real value: a bounded time window (ten minutes), a hard cap (100 events), and an explicit privacy/data statement ('No page contents are recorded'). It stops short of stating ordering, whether the call is side-effect free, what an event record contains, or what happens when the window is empty.

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 tight sentence with the object of the read front-loaded and the constraints in parentheses, plus one short clause on data content. No filler and nothing buried.

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?

For a simple, parameterless read tool this is close to adequate, and the time/count bounds are the key operational facts. Because there is no output schema, the description ideally would sketch the shape of an event record, and it says nothing about ordering or empty results, leaving a real gap for an agent that must interpret the response.

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 beyond the fixed time window and result cap, which it already states. Baseline 4 applies for a parameterless 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 verb and resource ('Read recent human-takeover events') and states the governing scope (last ten minutes, up to 100), which is concrete enough to act on. It does not explicitly contrast with any sibling, but no sibling in the list plausibly covers takeover events, so the risk of misselection is low.

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 the tool to poll for human-takeover detection because of the 'human-takeover events' framing and the ten-minute window. There is no explicit statement of when to call it versus other observation tools (e.g., browser_observe or browser_snapshot), nor any precondition or polling-frequency guidance.

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