Skip to main content
Glama
Brave Session MCP

Brave Session MCP

by MacStenk

brave_tabs

Read-only

Lists open tabs in the shared Brave browser session, letting AI agents identify and navigate available pages while keeping existing logins intact.

Instructions

Listet offene Tabs im freigegebenen Brave auf. Bestehende Anmeldungen bleiben im 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": "brave_tabs"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The second sentence adds real context beyond that: existing logins/sessions persist, meaning the call does not disturb browser state. However, it says nothing about the ordering, filtering, or stability of the listing, and no output schema exists to cover the result shape.

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?

Two short sentences with the core action front-loaded and no filler. The session-persistence note is relevant but placed without a connective, so it reads as a detached remark rather than integrated guidance.

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 carries the burden of explaining what a caller gets back — titles, URLs, tab identifiers — which matters greatly because sibling tools like brave_click and brave_close presumably need a tab reference from this listing. That linkage is missing, so the definition is only adequate for a discovery step that feeds a larger workflow.

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 and the description correctly describes a parameterless operation, so there is nothing to mis-specify. Baseline 4 applies for a no-parameter 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 gives a specific verb plus resource ("Listet offene Tabs im freigegebenen Brave auf") and scopes it to the shared Brave instance, so an agent can tell it apart from action siblings like brave_click or brave_navigate. It stops short of contrasting with the closest read-oriented siblings (brave_read, brave_status), which would make selection fully unambiguous.

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 explicit when-to-use statement, no when-not-to-use case, and no named alternative. The agent must infer from the verb alone that this belongs at the start of a browsing workflow, before read/click/close.

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