Skip to main content
Glama
Sign In
spectra-mcp

spectra-mcp

by LowOrbitLab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

browser_activate_tab

Switch the agent browser to an existing tab by page_id, letting the agent interact with the correct page.

Instructions

Switch the agent browser to an existing tab by page_id.

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": {
      "page_id": "<page_id>"
    },
    "name": "browser_activate_tab"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idYes
session_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does not state what happens on an invalid or closed page_id, how session_id affects targeting, whether the switch is idempotent, or what the resulting active-tab state 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?

A single tight sentence with the selector front-loaded and no filler. 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?

An output schema exists, so return values need not be explained, and the required-parameter contract is simple. However, the undocumented session_id and the absence of any failure or state-transition behavior leave gaps for a tool with no annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for two parameters. The description mentions page_id as the selector but adds no format, range, or source detail, and session_id is entirely absent from the description despite having a default value.

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 ('Switch') and resource ('agent browser tab') plus the identifier used ('by page_id'). It is reasonably distinguishable from browser_list_tabs, though it doesn't explicitly name siblings.

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?

No when-to-use or when-not-to-use guidance is given, and no alternative tools are named. Usage is only implied: an agent would have to infer that this follows browser_list_tabs and precedes interaction tools.

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