Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

listEnvs

Retrieve browser environments with filters for name, status, group, proxy, and creation time, plus pagination and optional details to locate and manage profiles.

Instructions

List environments

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

Input Schema

NameRequiredDescriptionDefault
allNo
nameNo
detailNo
remarkNo
statusNo
page_noNo
group_idNo
page_sizeNo
proxy_hostNo
serial_numNo
platform_userNo
operate_statusNo
end_create_timeNo
start_create_timeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

D1.8/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 burden and discloses almost nothing. It does not state that the operation is read-only, how pagination behaves, what the defaults are for the many filter parameters, or whether results are truncated at page_size.

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?

At two words the text is short but not concise in any useful sense; it is under-specified rather than efficient. There is no structure to speak of, no front-loaded scope, and no sentence that adds information beyond the title.

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 14-parameter filtered list tool with no annotations, no output schema, and no parameter documentation needs far more description than this. An agent cannot determine filtering behavior, pagination, result shape, or the meaning of key flags from the definition as given.

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?

There are 14 parameters with 0% schema description coverage, and the description says nothing about any of them. Names like "all", "detail", "operate_status", and "proxy_host" carry ambiguous semantics that neither the schema nor the description resolves.

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?

The description restates the tool name verbatim as "List environments" and adds no scope, no resource detail, and no distinction from sibling tools such as listEnvGroups. An agent learns only that it enumerates environments, with no idea what the listing covers or how it differs from its neighbors.

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 alternatives like listEnvGroups, and no stated preconditions. The only cue is the implied read operation from the word "List"; everything else is left to inference.

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