This server has critical definition gaps. Tool descriptions are present but minimal (10-40 chars, well below the 50-200 char LLM-optimized baseline). Input schemas are either missing entirely or severely incomplete. The `edit_diagram` tool has an array parameter with no item schema. The `get_shape_library` tool has empty input schema. No output schemas are documented. Parameter descriptions are generic and lack actionable constraints. No error handling guidance. The server appears to be a Next.js UI wrapper around draw.io, not a proper MCP server with well-defined tool contracts.

• Expand tool descriptions to 80-150 chars. Example for `display_diagram`: 'Render a diagram from draw.io XML. Returns the diagram ID and display URL. Use this after generating or modifying diagram XML to preview changes.'
• Document output schemas for all tools. Specify what fields are returned (e.g., diagram_id, url, shape_count) and their types. This enables LLMs to chain tools correctly.
• Add detailed parameter descriptions with constraints. For `edit_diagram`, specify: 'Array of operation objects. Each operation must have: {type: "add"|"remove"|"update", target: string, properties: object}. See get_shape_library for valid shape types.'
• Add error handling guidance. Example: 'If XML is malformed, returns error with line number. If diagram exceeds size limit (10MB), returns error with current size. Retry with smaller XML or split into multiple diagrams.'
• Define the `operations` array schema explicitly in JSON Schema. Include minItems, maxItems, and item schema with required fields and allowed operation types.