Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

get_windows_and_tabs

Retrieves all currently opened windows and tabs for a specified browser environment ID, enabling inspection of active browser sessions.

Instructions

Get all currently opened windows and tabs in the browser environment

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": "get_windows_and_tabs"
  }
}

Input Schema

NameRequiredDescriptionDefault
envIdYesEnvironment ID for the browser environment to operate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It conveys only that results are limited to currently open windows/tabs; it says nothing about permissions, whether the environment must have an active session, whether the result nests tabs under windows, or how large result sets are handled.

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?

One short sentence with the resource and scope front-loaded and zero filler. Nothing would need to be removed.

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 (one required parameter, fully documented schema), but there is no output schema, so the description should at least hint at the return shape (windows containing tabs). As written it is adequate to invoke but leaves the agent guessing what comes back.

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% for the single envId parameter, so the baseline is 3. The phrase 'in the browser environment' loosely ties the call to envId but adds no format or constraint detail beyond the schema.

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 and resource ('Get all currently opened windows and tabs') plus a scope qualifier ('in the browser environment'), so an agent can tell this is an enumeration tool distinct from the mutating sibling close_tabs. It stops short of naming or contrasting any sibling explicitly.

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 when-to-use or when-not-to-use guidance, and no mention of alternatives such as close_tabs, which is the obvious complement to a list-tabs tool. The read-only intent is only weakly implied by the verb 'Get'.

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