This server has fundamental definition quality gaps across nearly all dimensions. While 13 tools are registered, most lack proper input/output schema visibility in the Python code, descriptions are generic and often trivial, and there is no evidence of parameter documentation or error handling guidance. The server appears to auto-generate tool definitions from JavaScript command definitions (command_definitions.js), but the Python registration layer (src/tapir/parser.py is not shown) is opaque, we cannot verify how schemas are actually bound to the MCP tool definitions. Only TestConnection is explicitly visible in Python with a direct @mcp.tool() decorator; the other 12 tools are inferred from JavaScript comments without visible Python registration. This breaks the 'actual tool definition visibility' requirement and caps those tools at 50 individually. Even so, they score poorly because descriptions are brief but non-trivial (60-80 chars typically), parameter descriptions are present in some schemas (SetProjectInfoField, OpenProject) but missing in others (GetStories has complex nested schemas with no parameter guidance), and error handling is completely absent. The server targets Archicad (a CAD application) and offers legitimate domain tools (GetProjectInfo, SetStories, OpenProject) but the implementation quality is well below production baseline.

• Add explicit Python @mcp.tool() registrations for all 12 tools currently inferred from JavaScript. Use fastmcp decorators to bind schemas, descriptions, and parameter documentation directly in the Python layer. This makes tool definitions verifiable and maintainable.
• Expand TestConnection description to 50+ chars explaining what a successful connection test reveals and when to call it (e.g., 'Verifies that the MCP server can communicate with the running Archicad instance. Call this first to confirm Archicad is accessible.').
• Add input schema to TestConnection (currently empty {}). If it truly takes no parameters, explicitly define this as {'type': 'object', 'properties': {}, 'required': []} with a note that it connects to the default Archicad instance.
• For QuitArchicad, implement a confirmation pattern: add a 'confirm' parameter (boolean, default false) or split into two tools: QuickQuitArchicad (immediate, dangerous) and RequestQuitArchicad (safe, confirmation required). Add error guidance such as 'QuitArchicad will terminate the running Archicad process, unsaved work will be lost. Always confirm user intent before calling.'
• Resolve $ref references in GetCurrentWindowType and GetStories. Either inline the WindowType and StoriesParameters definitions in the schema, or document what fields they contain in the description.
• For SetStories, define the 'stories' parameter schema with explicit field types, constraints, and examples. E.g., 'stories: object with properties {firstStory: number, lastStory: number, ...}. See Archicad documentation for valid story parameters.'