Skip to main content
Glama
Brave Session MCP

Brave Session MCP

by MacStenk

brave_navigate

Destructive

Navigates a specifically selected browser tab to an HTTP(S) URL and optionally waits for the page to load before returning.

Instructions

Navigiert einen ausdrücklich ausgewählten Tab zu einer HTTP(S)-Adresse. wait wartet danach zusätzlich ab.

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>",
      "url": "<url>"
    },
    "name": "brave_navigate"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
waitNoMillisekunden, die nach der Aktion auf das Laden der Seite und eine Beruhigungsphase gewartet wird. Weglassen oder 0: sofort zurückkehren.
tabIdYesStabile Tab-ID aus brave_tabs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=true, so the safety profile is carried by structured data. The description adds almost nothing beyond that: the second sentence ('wait wartet danach zusätzlich ab') only restates what the schema's wait parameter already documents, and it never mentions that the current page content is replaced or what happens on invalid/unreachable URLs.

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 primary action front-loaded and the URL target stated first. The trailing sentence about wait is somewhat redundant with the schema and is the only real padding.

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

Completeness4/5

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

For a three-parameter navigation tool whose annotations already flag mutation, open-world access and destructiveness, and whose schema documents two of three parameters, the description covers the essential action adequately. Missing are only secondary details such as the fate of the current page or error behavior, which the annotations partially mitigate.

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 coverage is 67%: tabId and wait are already documented in the schema, including the millisecond range and the 'omit or 0 = return immediately' behavior, so the description's brief note on wait is largely redundant. It also omits tabId entirely, so it adds little meaning beyond the structured fields — the baseline 3 for a well-described schema is the right level.

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 uses a specific verb ('Navigiert') plus the resource it acts on ('einen ausdrücklich ausgewählten Tab') and the target ('HTTP(S)-Adresse'), so the action is unambiguous. The qualifier 'ausdrücklich ausgewählt' implicitly separates it from tools that create a new tab, but no sibling (e.g. brave_open) is named to make the distinction explicit.

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: 'ausdrücklich ausgewählten Tab' signals that a tab must already be known/selected, which hints at using brave_tabs first, but there is no explicit when-to-use, when-not-to-use, or named alternative for opening a fresh tab. The schema picks up some of this slack by pointing tabId at brave_tabs, but the description itself leaves routing to inference.

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