Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

openEnv

Launches a specified DICloak browser environment by env ID, with optional headless mode, so AI assistants can start profile sessions for automation.

Instructions

Open 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": "openEnv"
  }
}

Input Schema

NameRequiredDescriptionDefault
envIdYes
headlessNoWhether to open in headless mode

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.7/5.0
Behavior1/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, yet it discloses nothing about what "open" does: whether it starts a process, allocates a session, changes persisted state, requires auth, or is reversible. It also says nothing about what happens when envId is invalid or already open.

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 two-word description is technically concise but is under-specified rather than efficiently informative. It lacks the front-loaded detail an agent needs to decide whether and how to call the tool.

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

Completeness1/5

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

For a lifecycle/session tool with two parameters, 50% schema coverage, no annotations, and no output schema, the definition is far too thin. It omits the semantics of envId, the effect of opening, and any distinction from the many sibling environment-management tools.

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 coverage is only 50%: the schema documents headless but leaves envId undocumented as just a string. The description adds no meaning for envId (e.g., identifier format, source, or valid values) and does not explain the headless tradeoff, so it fails to compensate for the coverage gap.

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?

"Open environment" restates the tool name (openEnv) without adding scope or distinguishing it from lifecycle siblings like closeEnv, deleteEnv, recoverEnv, or updateEnv. An agent knows the verb and resource only because the name already says them.

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 prerequisite or side-effect context, and no mention of alternatives such as closeEnv or deleteEnv. The agent must infer whether this creates a new environment, resumes an existing one, or launches a session.

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