Runs a stdio MCP server that formats XAML through XamlStyler.
XAML Styler MCP has clear, verb-prefixed tool names and consistent descriptions (avg 95 chars). All 5 tools have input schemas with typed parameters and descriptions. However, output schemas are not documented in the visible code, only return type names (XamlFileFormatResult, etc.) are declared. Parameter descriptions are adequate but lack format constraints, ranges, or examples of valid inputs. Error handling and recovery guidance are absent. No pagination, batching, or composition patterns evident. Tool annotations (ReadOnly, Destructive, UseStructuredContent) are present in code but not exposed in the MCP schema definition visible here.
Checks whether .xaml and .axaml files in a directory are already formatted.
Checks whether a .xaml or .axaml file is already formatted.
Formats XAML content and returns the formatted result.
Formats .xaml and .axaml files in a directory and optionally writes changes to disk.
Formats a .xaml or .axaml file and optionally writes changes to disk.
Output schemas not documented. Return types (XamlFileFormatResult, XamlDirectoryFormatResult, etc.) are declared but their field structure is not visible in the provided code. LLMs cannot plan downstream operations without knowing what fields to extract.
No error handling or recovery guidance. Tools lack descriptions of failure modes (e.g., 'file not found', 'invalid XAML', 'permission denied') and what the LLM should do next. Agents cannot self-correct on failures.
Parameter descriptions lack format constraints and examples. 'configPath' is described as 'Optional Settings.XamlStyler path' but does not specify file format, expected location, or what happens if the path is invalid. 'directoryPath' and 'filePath' lack guidance on absolute vs. relative paths.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 58 | 2025-06-18+ | v2 |
Destructive operations (format_xaml_file, format_xaml_directory) default writeChanges=true. This invites accidental data loss if an LLM omits the parameter. No confirmation or dry-run pattern is offered.
No batch operations. Formatting a directory with recursive=true may process hundreds of files in a single call, but no pagination, progress reporting, or per-file success/failure tracking is evident. Large operations risk context window exhaustion.