Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

switch_tab

Activate a specific browser tab in a DICloak environment by tab ID, title, or URL so automation continues in the correct page context.

Instructions

Switch to a tab in the browser environment by tab ID, title, or URL

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": {
      "envId": "<envId>"
    },
    "name": "switch_tab"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoSwitch to tab with matching URL (partial match). Either tabId, title, or url must be provided.
envIdYesEnvironment ID for the browser environment to operate.
tabIdNoTab ID (1-based index) to switch to. Either tabId, title, or url must be provided.
titleNoSwitch to tab with matching title (partial match). Either tabId, title, or url must be provided.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 behavioral burden and it falls short: it does not say whether switching brings the tab into focus or alters session state, nor what happens when a partial title/URL matches multiple tabs, or when no tab is found. These are exactly the ambiguities an agent needs resolved before calling a state-changing navigation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the action and its selector modes come first. It is not padded, though it is also too terse to earn a 5 given the unresolved behavioral questions.

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?

With no output schema expected and full schema coverage on all four parameters, the identifier mechanics are adequately covered. However, for a tab-activation tool with an environment scope and ambiguous partial matching, the description omits the outcome and failure behavior an agent would want.

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 description coverage is 100%, with each parameter already documenting its role including the partial-match semantics for url and title. The description merely echoes the selector list and adds no meaning beyond the schema, so baseline 3 applies.

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 to') and resource ('a tab in the browser environment') plus the three selector modes, so the action is unambiguous. It does not contrast itself with siblings like close_tabs, so an agent must infer that this is non-destructive navigation rather than tab management.

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?

The description and schema imply the preconditions (envId plus one of tabId/title/url), which tells an agent how to invoke it. It gives no explicit when-to-use versus when-not-to-use guidance and no mention of related sibling tools for tab lifecycle operations.

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