Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

saveEnvGroup

Creates a DICloak environment group from a required name and optional remark and member IDs, enabling organized browser profile and member management.

Instructions

Create 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": {
      "name": "<name>"
    },
    "name": "saveEnvGroup"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesEnvironment group name
remarkNoRemark
member_idsNoList of member IDs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/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 only implies a mutation. It says nothing about required permissions, whether duplicate names are rejected, whether members are validated, or what happens on failure — all material for a create/write tool.

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?

Three words, front-loaded with the verb, so nothing is wasted — but the brevity reflects under-specification rather than disciplined concision. There is no structure to convey scope, constraints, or outcome.

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?

This is a 3-parameter write operation with no annotations and no output schema, so the description must explain side effects and result shape; it explains neither. An agent would have to call it blind regarding what is created and what is returned.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so name, remark, and member_ids are already documented in the input schema; the description adds no semantics beyond it. Per the high-coverage baseline, a 3 is appropriate rather than lower.

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 gives a verb and resource ("Create" + "environment group"), which is more than a bare restatement of saveEnvGroup, but it never explains what an environment group is or how it differs from siblings such as updateEnvGroup or saveMember. An agent can infer this is a create operation on a grouping entity, but nothing more.

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 (e.g. whether the environment must exist or be open), and no reference to alternatives like updateEnvGroup for existing groups. The agent must guess the context entirely.

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