Skip to main content
Glama
Sign In
X-Ways MCP

X-Ways MCP

by Donovoi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

build_path_usage_pattern_triage_command

Build a local sanitizer command for triaging path usage patterns from XwfPathExport JSONL output.

Instructions

Build, but do not run, the local sanitizer command for XwfPathExport JSONL output.

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": {
      "jsonl_path": "<jsonl_path>",
      "report_directory": "<report_directory>"
    },
    "name": "build_path_usage_pattern_triage_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
jsonl_pathYes
report_directoryYes
run_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, and the description only states the tool builds a command. It does not disclose side effects, permissions, or what the command does beyond being a 'sanitizer'. Minimal behavioral insight.

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, efficient sentence that front-loads the key action ('Build, but do not run'). No wasted words.

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 (not provided), the description is too brief for a tool with 3 parameters and low schema coverage. It lacks details on parameter meanings, command output, and typical use cases.

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?

The description does not explain any parameters. Schema description coverage is 0%, so the description should compensate but fails to. It only hints that 'jsonl_path' relates to XwfPathExport output, but leaves 'report_directory' and 'run_id' unexplained.

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 action ('Build') and the resource ('local sanitizer command for XwfPathExport JSONL output'). It distinguishes from siblings like 'run_path_usage_pattern_triage' by specifying '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 explicitly says 'but do not run', providing a clear usage guideline. It implies that running is done elsewhere (sibling tool), but does not explicitly list alternatives or when-not conditions.

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