Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

deleteEnv

Deletes a DICloak browser environment using its envId to remove unused profiles from the local client.

Instructions

Delete 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": "deleteEnv"
  }
}

Input Schema

NameRequiredDescriptionDefault
envIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.9/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. The word "Delete" at least signals a destructive mutation, but it doesn't say whether the environment is recoverable, whether recoverEnv can undo it, what permissions are needed, or what happens to resources inside the environment.

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?

Although it is very short, it is short only because of under-specification, not efficiency. There is nothing to front-load, and the single phrase tells the agent almost nothing it couldn't infer from the name.

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?

A destructive tool with no annotations, no output schema, and an entirely undocumented parameter requires far more than three words. It doesn't say what gets destroyed, whether it can be undone, or how it relates to deleteEnvCompletely, so an agent cannot safely call it.

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 schema has one required parameter (envId) at 0% description coverage, and the description never mentions it or adds any meaning beyond its type. There is no format hint, no indication of what kind of identifier it is, or whether it accepts names, and thus nothing compensates 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?

"Delete environment" just restates the tool name deleteEnv as a sentence, with no added scope, so it is essentially tautological. It also fails to distinguish itself from the sibling deleteEnvCompletely, which suggests a different deletion semantics, or from closeEnv/recoverEnv. An agent can't tell from the description whether this is a soft, partial, or full deletion.

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 exclusions, and no pointer to any alternative. The presence of both deleteEnvCompletely and recoverEnv makes the missing guidance consequential, but nothing in the description is misleading.

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