Skip to main content
Glama
Sign In
chromaphore-mcp

chromaphore-mcp

Official
by nodriver-project
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Select a tab

tab_select

Activates a browser tab by ID to bring it to the front and make it the active target for other tools; use tab IDs from the tab list.

Instructions

Brings a tab to the front and makes it the one the other tools act on. Tabs the page opened appear in tab_list.

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": {
      "tab": "<tab>"
    },
    "name": "tab_select"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabYesA tab id from tab_list, such as t2.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are supplied, so the description must carry the behavioral burden. It clearly discloses the main effects: the selected tab is brought to the front and becomes the one other tools act on. It does not describe failure behavior for invalid or closed tab IDs, which is a minor gap for this simple operation.

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 two short sentences and front-loads the primary effect. Every sentence contributes useful information without repetition or filler.

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 single-parameter tool with no output schema or annotations, the description gives enough context to call it correctly: the effect, the active-tab targeting behavior, and where tab IDs come from. Only edge-case behavior for invalid tabs is omitted.

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 100%, and the schema already explains that the tab parameter is a tab ID from tab_list such as t2. The description reinforces the source of valid IDs but adds no syntax or format detail beyond the schema, so the baseline score of 3 is appropriate.

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?

The description gives a specific verb and resource: it brings a tab to the front and makes that tab the target for other tools. It also distinguishes the tool from tab_list by explaining that listing tools cover tabs opened by the page.

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 description makes clear that this tool is used to choose which tab subsequent actions affect, and that valid tab IDs come from tab_list. It does not give explicit when-not guidance or discuss alternatives such as tab_new, but the intended usage context is clear.

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

Deploy Server

Other Tools