Skip to main content
Glama

neuron_open_tab

Opens a new browser tab with an optional URL, enabling quick navigation or starting a browsing session from any MCP client.

Instructions

Open a new tab, optionally to a URL

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoURL to open (optional)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.4.1

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. It clearly discloses the primary side effect of opening a new tab, and the optional URL qualifier adds meaning. However, it does not mention whether the new tab becomes active, whether a blank tab opens when no URL is supplied, or what the return value is.

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?

The description is a single sentence, front-loaded with the action, and contains no filler or redundant information. Every word earns its place.

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?

The tool is simple, with one optional parameter and no output schema, so extensive documentation may not be required. Still, the description omits details that would help an agent invoke it confidently, such as what happens when URL is omitted, whether the tab is focused, and what result is returned.

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?

The schema already describes the single parameter as 'URL to open (optional)' with 100% coverage. The description's phrase 'optionally to a URL' adds no additional semantic detail such as URL format, default behavior, or validation rules, so the baseline schema coverage determines the score.

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 states a specific verb ('Open') and resource ('a new tab'), and clarifies the optional URL behavior. It does not explicitly name sibling alternatives like neuron_navigate, but 'new tab' makes the distinction reasonably clear.

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 guidance on when to use this tool versus alternatives such as neuron_navigate, neuron_reload, or neuron_list_tabs. The description gives no context about switching tabs or invoking the current tab versus opening a fresh one.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/conquext/neuron-inspector'

If you have feedback or need assistance with the MCP directory API, please join our Discord server