Skip to main content
Glama
Brave Session MCP

Brave Session MCP

by MacStenk

brave_status

Read-only

Checks shared local Brave access before an agent acts, without launching a browser or reading open tabs.

Instructions

Prüft den gemeinsamen lokalen Brave-Zugang, ohne einen Browser zu starten oder Tabs auszulesen.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuine behavioral context by ruling out browser launch and tab enumeration, i.e. it truly is a side-effect-free probe. It still does not disclose what 'status' actually comprises (installed? running? authenticated?) or whether it can be slow or fail.

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 front-loaded sentence with no filler: the action comes first and the scoping exclusions follow. Nothing is redundant with the title or with structured fields.

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 zero-parameter probe this is nearly enough, but there is no output schema, so the description is the only place that could say what a status result looks like and what conditions count as unavailable. That omission leaves the agent unable to interpret the result without calling the tool.

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; baseline 4 applies. The schema is an empty object and the description correctly implies no input is needed.

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?

States a specific verb+resource: checking the shared local Brave access ('gemeinsamen lokalen Brave-Zugang'). The parenthetical exclusions ('ohne einen Browser zu starten oder Tabs auszulesen') separate it from the browser-driving siblings such as brave_open or brave_tabs, though it remains slightly ambiguous whether 'Zugang' means installation, connectivity, or auth status.

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: the description makes clear this is a passive check rather than a browser action, which suggests calling it before the other brave_* tools. It never states when to prefer it, what a failure means, or what to do next, so the agent must infer the workflow.

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