Skip to main content
Glama
DICloak Local API MCP Server

DICloak Local API MCP Server

Official

deleteEnvGroup

Deletes an environment group by ID, with an option to also remove all environments inside it.

Instructions

Delete 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>",
      "del_env": "<del_env>"
    },
    "name": "deleteEnvGroup"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
del_envYesWhether to also delete environments in the group

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.1/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 says nothing about irreversibility, recovery, permissions, or the cascade behavior of del_env. The single verb does imply destruction, but that is the extent of the disclosure.

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 front-loaded phrase with zero waste, but that brevity reflects under-specification rather than disciplined editing. Nothing in the sentence beyond the name earns its place because there is nothing else.

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 destructive, cascading delete with no annotations and no output schema, the description is far too thin. It omits the consequence of del_env=true, which is the single most important fact an agent needs before calling it.

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 coverage is only 50%: del_env is described in the schema, but id is undocumented in both schema and description. The description adds no meaning to either parameter and does not explain that del_env can wipe the environments inside the group.

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?

"Delete environment group" restates the tool name (deleteEnvGroup) with no added scope or qualifier. The agent can infer a destructive operation on a group, but nothing distinguishes it from siblings like deleteEnv, deleteEnvCompletely, or closeEnv.

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 or when-not-to-use guidance, and no mention of alternatives such as deleteEnvCompletely or deleteEnv, which plausibly overlap. Usage is only implied by the verb.

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