X-Ways MCP

Overview Schema Source Related Servers Discussions Admin

testenv_destroy

Delete a managed disposable test environment only after confirmation is provided, cleaning up temporary fixtures for controlled automation.

Instructions

Delete a managed disposable fixture environment only when confirm=true.

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

Input Schema

Name	Required	Default
`name`	No	CASE-001
`evidence_os`	No	windows
`root`	No	test-envs
`confirm`	No
`missing_ok`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 24, 2026

TDQS

B3.3/5.0

Behavior3/5

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

The description indicates a destructive operation ('Delete'), but with no annotations, it lacks detail on side effects, reversibility, or safety nets. The condition on confirm is noted, but overall behavioral disclosure is minimal.

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?

Single sentence, front-loaded with the verb, and no extraneous text. Every word contributes to understanding.

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?

Despite having 5 parameters and no schema descriptions, the description fails to explain parameter roles or output. For a destructive tool, more context on behavior and result format is needed.

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?

With 0% schema description coverage, the description adds minimal parameter info—only referencing confirm for the deletion condition. Other four parameters (name, evidence_os, root, missing_ok) are left unexplained, requiring agent inference.

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 the tool's action ('Delete') and target ('a managed disposable fixture environment'), with the key condition ('only when confirm=true'). This distinguishes it from sibling tools like testenv_create or testenv_list.

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?

No guidance on when to use this tool versus alternatives (e.g., testenv_build, testenv_create). The description only specifies a condition for execution but omits context about prerequisites or scenarios.

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