The server implements 8 IFC-domain tools with basic structure but significant quality gaps. Tool names follow the verb_noun convention (e.g. get_entities, get_entity_properties), which is good. However, parameter descriptions are inconsistent: some tools have minimal descriptions (e.g., 'greet' has null description for 'name'), and critical domain-specific context is missing. The 'greet' tool is a placeholder with no business value in an IFC server. Most importantly, NO OUTPUT SCHEMAS are documented anywhere in the source code, neither in docstrings nor in schema declarations. Without documented output structure, LLMs cannot predict what fields to expect, breaking downstream tool composition and forcing agents to guess. Error handling is present but generic ('error, the file is not found or broken') without recovery guidance. Parameter constraints (e.g., valid entity types, path format requirements) are mentioned in descriptions but not formalized as enums or patterns.

• ADD EXPLICIT OUTPUT SCHEMAS to every tool. Use Python type hints (e.g., `-> list[dict[str, Any]]` or `-> dict[str, float]`) and document in docstrings. Example for get_entities: 'Returns: list of dicts with keys globalId (str), name (str), type (str).'
• FORMALIZE ENTITY TYPE CONSTRAINTS. Replace description 'e.g., "IfcDoor"' with an enum of valid IFC entity types, or a regex pattern constraint. Prevents LLM hallucination of invalid types.
• REPLACE GENERIC ERRORS WITH ACTIONABLE MESSAGES. Instead of 'error, the file is not found or broken', return 'File not found at {file_path}. Verify the path is absolute or relative to the server's working directory. Supported formats: .ifc (IFC 2x3, IFC 4.0).'
• ADD PARAMETER DESCRIPTIONS WHERE MISSING. Example: greet's 'name' parameter should be 'A person\'s name (string, any length). Used to personalize the greeting.'
• DOCUMENT PAGINATION AND LIMITS FOR LARGE RESULT SETS. If get_entities_in_spatial returns thousands of entities, add page/offset/limit params and cap results at 100. Document: 'Returns up to 100 globalIds; use offset to fetch more.'
• REMOVE OR REPURPOSE 'greet' TOOL. Either delete it or replace with domain-specific utility (e.g., 'validate_ifc_file' with input file_path, output validation status + errors).
• DEFINE IFC-SPECIFIC PARAMETER FORMATS. Document required format for file_path (absolute vs relative, supported extensions), globalId (UUID format, case-sensitivity), and property names (case-sensitive, allowed prefixes).
• ADD EXAMPLE OUTPUTS TO DOCSTRINGS. Show LLM what a successful call returns: 'get_entities returns: [{"globalId": "2f643d53-...", "name": "Door_01", "type": "IfcDoor"}, ...]'.