Skip to main content
Glama

browser_mark

Mark a browser tab as a deliverable or handoff without switching focus or closing it.

Instructions

Mark a tab as a deliverable or handoff without changing focus or closing it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tabId": "<tabId>",
      "mark": "<mark>"
    },
    "name": "browser_mark"
  }
}

Input Schema

NameRequiredDescriptionDefault
markYes
tabIdYesTab id from browser_tabs.
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

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does add real behavioral context by scoping the side effect: the tab is not focused and not closed, so the call is non-disruptive. It stops short of saying whether the mark persists across sessions, whether it can be removed or overwritten, or what the call returns.

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 sentence with the action and the tab-state constraint front-loaded, and zero redundant or filler wording. Nothing needs to be trimmed.

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 3-parameter tool with no output schema and no annotations, the description covers the main risk (disrupting the tab) but leaves the post-call story unclear: where the mark surfaces, whether it is reversible, and how to unmark. Adequate but with clear gaps.

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?

Schema coverage is 67%: tabId and browser already carry descriptions pointing at browser_tabs and browser_list. The description adds no meaning to the 'mark' enum beyond restating its two values, so it does not explain what distinguishes a deliverable from a handoff, but with two of three parameters documented and an enum constraining the third, the baseline is met.

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

Purpose5/5

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

States a specific verb ('mark') on a specific resource ('a tab') with the two allowed target states named ('deliverable or handoff'). It also distinguishes itself from neighboring behaviors by negating them ('without changing focus or closing it'), which lets an agent separate it from browser_focus and browser_close without reading either schema.

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 negated clause implies when this tool is preferable to focusing or closing a tab, which is useful implied guidance. However, there is no explicit when-to-use statement, no guidance on choosing between the two mark values, and no mention of prerequisites such as needing an existing tab id from browser_tabs.

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