Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

close_tabs

Closes browser tabs in a DICloak environment by tab ID, URL, active tab, or all tabs, enabling automated tab cleanup and browser task management.

Instructions

Close specified 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": "close_tabs"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoClose tabs matching this URL. Can be used instead of tabIds.
envIdYesEnvironment ID for the browser environment to operate.
tabIdsNoArray of tab IDs to close. If not provided, will close the active tab.
closeAllNoWhether to close all tabs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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 and mostly fails it. It does not disclose precedence when url, tabIds, and closeAll are combined, what happens when no selector is given (the schema says the active tab, not the description), whether closing is reversible, or whether the environment/session survives closing tabs.

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 or redundancy. It is efficient, though its brevity reflects under-specification rather than disciplined editing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter mutation tool with no annotations and no output schema, the description is thin. It says nothing about the interaction between the mutually substitutable selectors, about which tabs were actually closed, or about failure modes, all of which an agent needs before invoking it.

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%, so all four parameters are already documented in the schema, including the active-tab default for tabIds and the url-as-alternative note. The description adds no meaning beyond that, which fits the baseline 3.

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 concrete verb and resource: 'Close specified tabs in the browser environment.' An agent can tell this is a tab-level close operation rather than an environment-level one like closeEnv, though the description never names that sibling to make the distinction explicit.

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 guidance at all: nothing says when to close a single tab versus using closeAll, versus closing the whole environment via closeEnv. The reader must infer the routing decision entirely from the name and schema.

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