Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

updateEnvGroup

Updates a DICloak environment group by ID, letting you change its name, remark, and member IDs to keep browser profile groups accurate.

Instructions

Update environment group

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": "<name>"
    },
    "name": "updateEnvGroup"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
nameYesEnvironment group name
remarkNoRemark
member_idsNoList of member IDs

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 supplied, so the description carries the full behavioral burden, and it only implies mutation via the word 'Update'. It does not say whether this is a partial or full replacement, whether omitted fields are preserved, whether member_ids overwrites or appends to the existing membership, or what permissions are required.

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?

It is a single short phrase with no wasted words, but the brevity comes from under-specification rather than discipline. There is no structure to front-load because there is almost no content.

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 four-parameter mutation tool with no annotations and no output schema, the description is far too thin: no change semantics, no side effects, no confirmation of what is returned. The agent cannot safely predict the effect of the call from this definition.

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?

At 75% schema description coverage, the schema already labels name, remark, and member_ids, and the description adds nothing on top of it. The one genuinely ambiguous point for an update tool — whether member_ids replaces or augments the current member list — is left unresolved in both places.

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 verb and a resource ('Update environment group'), so the general action is graspable. But it is essentially the tool name decompressed, with no scope, no indication of what fields can be changed, and no differentiation from siblings such as saveEnvGroup or updateEnv.

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 at all: no statement of preconditions (does the group need to exist?), no contrast with saveEnvGroup or deleteEnvGroup, and no exclusions. The agent must infer the call context 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.