Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

closeEnv

Closes a DICloak browser environment by its env ID, ending the running profile session through the Local API.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
envIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2/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 of behavioral disclosure, and it says nothing beyond the single word "Close". It does not state whether running processes or sessions are terminated, whether state is preserved, whether the operation is reversible, or what permissions are required.

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

Conciseness2/5

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

The text is a single fragment with no wasted words, but here brevity comes from under-specification rather than economy. There is no front-loaded statement of effect, scope, or consequence to anchor the call.

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 lifecycle/teardown tool with one required, undocumented parameter, no annotations, and no output schema, the description is not complete enough to call the tool safely. At minimum it should distinguish close from delete and note reversibility, yet it supplies none of that.

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% and the description does not compensate: envId is never explained in terms of format, where to obtain it (e.g., from openEnv or listEnvGroups), or what happens if it is invalid. The only meaning conveyed is the parameter's self-evident name.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Close environment" only expands the tool name into a two-word phrase; it names a verb and resource but adds no scope, no object detail, and no distinction from siblings such as deleteEnv, deleteEnvCompletely, or close_tabs. An agent cannot tell from this text what closing means relative to those alternatives.

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 guidance, no prerequisites, and no mention of alternatives. With siblings like deleteEnv and deleteEnvCompletely present, the absence of any routing hint leaves the agent to guess whether close is a soft stop, a teardown, or a recoverable action (recoverEnv exists, hinting close may be recoverable, but the description never says so).

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