Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

getEnvGroupDetail

Retrieve details for a specific environment group by its ID, so you can inspect group settings and configuration before managing browser profiles or automation tasks.

Instructions

Get environment group 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": {
      "id": "<id>"
    },
    "name": "getEnvGroupDetail"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/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 disclosure burden, yet it reveals nothing about read-only safety, authentication/tenant scoping, or behavior when the id does not exist. Only the bare verb 'Get' implies a non-mutating read.

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?

The description is a single short sentence with no filler, so it is efficiently structured. Its brevity reflects under-specification rather than wasted wording, which is penalized in other dimensions.

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?

For a lookup tool with an undocumented parameter, no annotations, and no output schema, the description provides nothing about return content, error cases, or scope. An agent could not reliably predict what it receives back.

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 description coverage is 0% and the single required parameter is a bare 'id' string. The description does not say whether this is a numeric group id, a name, or a workspace-scoped identifier, leaving the only parameter ambiguous.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a verb+resource ('Get environment group details'), but it is essentially a restatement of the tool name with no added specificity. It does not clarify whether 'details' means members, proxies, settings, or all of them, nor how it differs from siblings such as getEnvInfo or listEnvGroups.

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 mention of prerequisites, and no reference to alternatives like listEnvGroups for enumeration. An agent must infer usage entirely from the name.

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