Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

getEnvInfo

Retrieves environment details for a given environment ID from DICloak's Local API, enabling AI assistants to identify profile context before managing browser profiles or automating tasks.

Instructions

Get environment details

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

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 supplied, so the description carries the full behavioral burden, yet it discloses nothing about permissions, whether a missing/invalid env triggers an error, or what the returned data looks like. Only the weak implication of "get" that this is a read operation is present.

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

Conciseness3/5

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

A single four-word sentence with no filler or redundancy, so it is not bloated. However, its brevity comes from under-specification rather than efficiency — there is no structure or front-loaded useful information to speak of.

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?

The tool is simple (one required parameter, no output schema), but the definition supplies none of what an agent needs: no description of the required identifier, no indication of the return payload, and no behavioral context to substitute for the absent annotations.

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?

Schema description coverage is 0% and the single required parameter envId is completely undocumented in the schema. The description does not mention envId at all, so it does not compensate for the gap — the agent cannot tell what an environment ID is or where to obtain one.

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?

"Get environment details" restates the tool name (getEnvInfo) almost verbatim and never says which details are returned. It gives no basis for distinguishing this from the many sibling getters such as getEnvGroupDetail or getMemberInfo.

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 when another env tool (getEnvGroupDetail, listEnvGroups, openEnv) would be the better call. The agent must infer everything from the name alone.

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