Skip to main content
Glama
Brave Session MCP

Brave Session MCP

by MacStenk

brave_close

Destructive

Closes only tabs opened by the agent, while preventing closure of user-owned tabs.

Instructions

Schließt einen Tab, den ein Agent selbst mit brave_open geöffnet hat. Tabs des Nutzers lassen sich nicht schließen.

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

Input Schema

NameRequiredDescriptionDefault
tabIdYesStabile Tab-ID aus brave_tabs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is carried structurally. The description adds real context beyond that: the eligible set is restricted to agent-opened tabs, which tells the agent the call will fail on user tabs. It does not say what error or result is returned on such a refusal, leaving a modest gap.

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?

Two short sentences, no filler, with the scope restriction front-loaded right after the action. Every clause carries information the agent needs.

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 one-parameter destructive tool with annotations covering safety and a fully documented schema, the description supplies the one non-obvious fact: only self-opened tabs are closable. Only the failure behavior when the precondition is violated is left unspecified.

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?

With a single required parameter and 100% schema description coverage, the schema already defines tabId and even points to brave_tabs as its source. The description adds no further syntax or format detail, so the baseline of 3 applies.

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 plus resource ('Schließt einen Tab') and immediately scopes it to tabs an agent opened itself via brave_open. That scope clause is what separates it from siblings like brave_open or brave_tabs without requiring the schema to be opened.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The second sentence effectively encodes a when-not rule: user tabs cannot be closed, so an agent knows not to attempt this on arbitrary tabs. It stops short of naming an alternative for tabs the agent didn't open (none may exist), so context is clear but explicit routing is absent.

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