Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

listEnvGroups

Retrieve environment groups with optional name, member, ID, remark, detail, and pagination filters to locate and organize browser profile groups.

Instructions

List environment groups

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "listEnvGroups"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNo
nameNo
detailNo
env_idNo
remarkNo
page_noNo
member_idNo
page_sizeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.8/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 burden, yet it says nothing about pagination behavior, whether the `all` flag overrides paging, what fields are returned, or permission requirements. With eight parameters and an implicit paging model, this is a substantial disclosure gap.

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?

The sentence is short but not concise in the useful sense: it is under-specified rather than efficient. There is no front-loaded scoping or filter summary to anchor the call.

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 tool with eight undocumented parameters, no annotations, and no output schema needs far more description than four words. Nothing an agent needs in order to build a correct query is present.

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% across eight parameters, and the description mentions none of them. The agent has no explanation of what `all`, `detail`, `member_id`, `env_id`, or `remark` mean or how they interact when combined.

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 names a specific verb (List) and resource (environment groups), so the agent can tell it retrieves collections. However, it offers no differentiation from siblings such as listEnvs or getEnvGroupDetail, and adds nothing beyond what the tool name already says.

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 guidance on when to use this instead of getEnvGroupDetail or listEnvs, and no mention of prerequisites or typical call scenarios. The agent must infer intended 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.