Skip to main content
Glama
Sign In
coalesce-transform-mcp

coalesce-transform-mcp

Official
by Coalesce-Software-Inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Delete Environment

delete_environment
Destructive

Permanently delete a Coalesce environment by providing its ID. Confirmation is required to prevent accidental deletion.

Instructions

Permanently delete a Coalesce environment. This is destructive and cannot be undone.

Args:

  • environmentID (string, required): The environment ID to delete

  • confirmed (boolean, optional): Set to true after the user explicitly confirms deletion

Returns: Confirmation message.

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": {
      "environmentID": "<environmentID>"
    },
    "name": "delete_environment"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmedNoSet to true after the user explicitly confirms the deletion.
environmentIDYesThe environment ID to delete

Output Schema

NameRequiredDescriptionDefault
idNo
nameNo
messageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.1

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description reinforces by stating 'permanently delete' and 'cannot be undone', and explains the confirmation mechanism. Adds value beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise: a single sentence stating purpose, then structured Args and Returns sections. Every sentence is necessary and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple destructive tool with an output schema, the description covers purpose, required parameters, confirmation requirement, and return type. No gaps.

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 coverage is 100%, so baseline 3. The description lists parameters in Args format, but adds no new information beyond what the schema already provides (e.g., 'confirmed' explanation is identical).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Permanently delete a Coalesce environment' with explicit verb 'delete' and resource 'environment'. It distinguishes from siblings like 'create_environment' by emphasizing destructiveness.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description warns this is destructive and irreversible, and explains the 'confirmed' parameter requires explicit user confirmation. It provides clear usage context but doesn't explicitly mention when not to use.

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

Deploy Server

Other Tools