Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

deleteEnvCompletely

Permanently deletes a specified DICloak browser profile environment by envId, removing it from the local client to free resources and prevent reuse.

Instructions

Delete environment permanently

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

Input Schema

NameRequiredDescriptionDefault
envIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/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. It discloses the one crucial trait — permanence/irreversibility — but says nothing about whether related resources (proxies, members, groups) are cascade-deleted, preconditions such as the env being closed, required permissions, or confirmation behavior expected of an agent before an irreversible action.

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?

Three words, front-loaded with the verb and resource, with no wasted phrasing. It is efficient but borders on under-specification for a destructive operation rather than being genuinely crisp and complete.

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?

For a one-parameter tool this is close to viable, and the irreversible nature is flagged. However, given zero annotations, no output schema, and an undocumented identifier parameter, an agent still cannot tell preconditions, side effects, or failure modes before committing an unrecoverable deletion.

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?

The single parameter envId has 0% schema description coverage, and the description adds no meaning: it does not say which identifier form is accepted or where to obtain it (e.g., from getEnvInfo or listEnvGroups). With one undocumented parameter, the schema provides nothing beyond the key name.

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?

The description states a specific verb and resource ('Delete environment') and adds the modifier 'permanently', which distinguishes it semantically from the sibling deleteEnv (implying a softer delete) and recoverEnv. It stops short of naming those siblings, so an agent must infer the distinction from the adverb alone.

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?

'Permanently' implies this is the irreversible variant, which is an implied usage rule, but the description never says when to choose this over deleteEnv, whether the environment must be closed first, or that recoverEnv cannot undo it. Guidance is inferable rather than stated.

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