Skip to main content
Glama
Sign In
X-Ways MCP

X-Ways MCP

by Donovoi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

build_case_db_path_string_triage_command

Constructs a PowerShell command to triage X-Ways case database path strings, without executing it.

Instructions

Build, but do not run, the local X-Ways case-DB path-string triage PowerShell command.

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

Input Schema

NameRequiredDescriptionDefault
search_rootNo
output_rootNo
throttle_limitNo
max_matches_per_fileNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description must carry the burden of behavioral disclosure. It only states 'build, but do not run' but does not describe the output, side effects, or permissions needed. The existence of an output schema is not leveraged in the description.

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 a single sentence that is front-loaded and concise. Every word is meaningful and avoids redundancy.

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 tool with 4 parameters and an output schema, the description is too minimal. It does not explain the output (what the built command looks like) or parameter roles, which is essential for an AI agent to use it correctly.

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 provides no explanation for any of the 4 parameters (search_root, output_root, throttle_limit, max_matches_per_file). The description adds zero value beyond the schema names.

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 verb 'Build' and the specific resource 'local X-Ways case-DB path-string triage PowerShell command'. It distinguishes from sibling tools like 'run_case_db_path_string_triage' by noting 'but do not run'.

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 implicitly tells when to use this tool (build without running) and contrasts with the run counterpart. However, it does not explicitly list alternatives or prerequisites.

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