Blockwright has 39 tools with consistent naming (verb_noun pattern) and basic descriptions, but critical gaps undermine quality. All tools lack input parameter descriptions, parameters are defined with type and description fields in schema, but descriptions are generic placeholders like 'Complete build input specification' or 'Build record to audit' that do not explain what values are valid, what format is expected, or when to use the tool vs. similar ones. No output schemas are documented anywhere. Parameter types are present (object, string, number) but lack constraints (enums, min/max, patterns). Error handling is absent, no guidance on retryability, user-fixable vs. fatal errors, or recovery steps. Tools like export_build_* are nearly identical, violating single-responsibility. The server exposes file system operations (discover_worlds, install_world_edit_schematic) without visible permission gates or audit logging. STDIO transport caps protocol readiness at 50.

• Add detailed parameter descriptions for every input parameter. For 'input' parameters accepting objects, specify required fields, valid values, and format constraints. Example: 'input: A build specification object with required fields: dimensions (object with width, height, depth as integers 1-256), materials (array of material names from list_palettes), and optional seed (string for reproducibility).'
• Document output schemas for all tools. Include field names, types, and descriptions. Example for compile_build: 'Returns {placement_record: object with fields: id (string), blocks (array of {x, y, z, material}), audit_metadata: {timestamp, seed_used, validation_status}}.'
• Consolidate export_build_* tools into a single export_build(build, format) tool where format is an enum: ['blueprint', 'schematic', 'litematic', 'mcfunction', 'csv', 'json']. This reduces cognitive load and eliminates redundant tool definitions.
• Add error handling guidance to tool descriptions. Example: 'Returns error if build is invalid (retryable: call validate_build_contract first) or if export format is unsupported (user-fixable: check format enum).'
• Implement confirmation/dry-run for destructive operations. Add a 'confirm' boolean parameter to delete_palette, install_world_edit_schematic, and revise_selected_region. When false, return a preview of what would be deleted/modified; when true, execute. Log all destructive operations with timestamp and caller context.

Inferred effective spec: 2025-06-18+.

• Relies on Stateful initialize / Mcp-Session-Id (removed; protocol is stateless) - make each request self-contained