X-Ways MCP

Overview Schema Source Related Servers Discussions Admin

testenv_build

Set up a disposable fixture environment and execute harness checks for triage and installation validation in X-Ways Forensics.

Instructions

Create a disposable fixture environment and immediately run harness checks.

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_build"
  }
}

Input Schema

Name	Required	Default
`name`	No	CASE-001
`evidence_os`	No	windows
`root`	No	test-envs
`cache`	No	truncated
`force`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 24, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations, the description carries full behavioral disclosure burden. It mentions 'immediately run harness checks' but does not describe what happens after checks (e.g., environment teardown, error behavior, side effects). The term 'disposable' is vague.

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?

The description is very concise (one sentence) but lacks structure and detail. It states the action but omits important context. Conciseness traded off against completeness.

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 an output schema and 5 parameters, the description provides no context on return values, parameter meanings, or operational flow. It is insufficient for an agent to use correctly without additional knowledge.

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

Parameters1/5

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

Schema description coverage is 0% and the description adds no information about any of the 5 parameters (name, evidence_os, root, cache, force). The description fails to explain how parameters affect the tool's behavior.

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 creates a disposable fixture environment and runs harness checks. It uses specific verbs and resources, and differentiates from siblings like testenv_create (which likely only creates without running checks) and testenv_run (which may run checks in existing environments).

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 is provided on when to use this tool versus alternatives such as testenv_create or testenv_run. The description does not mention prerequisites, when not to use, or context for decision-making.

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