X-Ways MCP

by Donovoi

Overview Schema Source Related Servers Discussions Admin

Local

cache_xways_manual

Cache and index the X-Ways manual locally to enable offline access and rapid lookup for forensic analysis.

Instructions

Cache and index the X-Ways manual locally for offline model lookup.

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

Input Schema

Name	Required	Description	Default
`source`	No
`cache_dir`	No
`refresh`	No
`download_latest`	No
`fetch_official_docs`	No
`timeout`	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 must disclose behaviors but only states the high-level purpose. It omits details about downloading, refreshing, side effects, permissions, or potential downtime.

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?

Single sentence is concise to a fault. It efficiently states purpose but underspecifies all other aspects, making it minimally adequate without being wasteful.

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?

Given 6 parameters with no schema descriptions, no annotation context, and an output schema, the description fails to provide sufficient detail for correct invocation. Lacks explanation of parameters, return value, and tool effects.

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 6 parameters (source, cache_dir, refresh, etc.). It adds zero value beyond parameter 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 action ('Cache and index') and the resource ('X-Ways manual'), with the benefit ('for offline model lookup'). It sufficiently distinguishes from sibling tools like 'search_xways_manual' or 'manual_status'.

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 like 'manual_status' or 'search_xways_manual'. Lacks cues for prerequisites, sequencing, or exclusions.

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