Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

recoverEnv

Recovers a browser profile environment by its envId to restore access after disruption or reset.

Instructions

Recover 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": "recoverEnv"
  }
}

Input Schema

NameRequiredDescriptionDefault
msgNo
codeNo
dataNo
nextNo
envIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.3/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the full behavioral burden, and it discloses nothing: not whether the operation mutates or destroys state, what permissions are needed, whether it is reversible, or what happens to an env that is not in a recoverable state.

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?

Two words are technically compact but represent under-specification rather than conciseness; there is no front-loaded explanation an agent could act on.

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 mutation-capable tool with five parameters, a nested object, no output schema, and no annotations requires a substantial description. What is present is completely inadequate for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Five parameters with 0% schema description coverage, including a nested object, and the description explains none of them. Even the required envId and the unexplained msg/code/data/next envelope fields are left undefined.

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?

"Recover environment" restates the tool name with no elaboration. It does not say what recovery means in this domain (restore from deletion, reset to a snapshot, re-open a closed env), nor how it differs from closeEnv, openEnv, updateEnv, or deleteEnv. Only the bare verb+resource is conveyed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 preconditions, and no mention of alternatives among the many sibling environment tools. The agent must guess whether recovery is even the right operation.

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