Skip to main content
Glama

get_ifc_total_structure

Retrieve complete IFC building model structure including spatial hierarchy and all physical elements like walls, doors, windows, columns, and beams to analyze building organization and components.

Instructions

Get the complete IFC structure including spatial hierarchy and all building elements.

This function extends the basic spatial structure to include building elements like walls,
doors, windows, columns, beams, etc. that are contained within each spatial element.
It provides a comprehensive view of how the building is organized both spatially and
in terms of its physical components.

Returns:
    A JSON-formatted string representing the complete hierarchical structure of the IFC model
    including spatial elements and their contained building elements, plus summary statistics

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler implementation for 'get_ifc_total_structure'. Connects to Blender via get_blender_connection(), sends the 'get_ifc_total_structure' command, formats the result as JSON, and handles errors.
    @mcp.tool()
    def get_ifc_total_structure() -> str:
        """
        Get the complete IFC structure including spatial hierarchy and all building elements.
    
        This function extends the basic spatial structure to include building elements like walls,
        doors, windows, columns, beams, etc. that are contained within each spatial element.
        It provides a comprehensive view of how the building is organized both spatially and
        in terms of its physical components.
    
        Returns:
            A JSON-formatted string representing the complete hierarchical structure of the IFC model
            including spatial elements and their contained building elements, plus summary statistics
        """
        try:
            blender = get_blender_connection()
            result = blender.send_command("get_ifc_total_structure")
    
            # Return the formatted JSON of the results
            return json.dumps(result, indent=2)
        except Exception as e:
            logger.error(f"Error getting IFC total structure: {str(e)}")
            return f"Error getting IFC total structure: {str(e)}"
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes what the tool returns (JSON-formatted string with hierarchical structure and summary statistics) and its scope (spatial elements and building elements). However, it does not cover potential behavioral traits like performance implications, error conditions, or data size limitations that might be relevant for a comprehensive structure tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured and appropriately sized. It starts with a clear purpose statement, elaborates on what the tool extends and includes, and ends with return details. Each sentence adds value without redundancy. It could be slightly more concise by combining some clauses, but overall it is efficient and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (comprehensive IFC structure) and lack of annotations and output schema, the description does a good job of covering key aspects: purpose, scope, return format, and differentiation from basic tools. It provides enough context for an agent to understand what the tool does and when to use it, though it could benefit from more behavioral details like performance notes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and schema description coverage is 100%. With no parameters to document, the description appropriately focuses on output semantics. It adds value by explaining what the return data includes (hierarchical structure, building elements, summary statistics) and the format (JSON-formatted string), which compensates for the lack of an output schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Get the complete IFC structure including spatial hierarchy and all building elements.' It specifies the verb ('Get'), resource ('complete IFC structure'), and distinguishes from sibling tools like 'get_ifc_spatial_structure' by emphasizing inclusion of building elements. The description explicitly contrasts with the basic spatial structure, making the differentiation clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use this tool: it 'extends the basic spatial structure' and is for obtaining a 'comprehensive view' of the building organization. It implies an alternative (the basic spatial structure tool) but does not explicitly name it or provide exclusion criteria. The guidance is sufficient to understand the tool's role but lacks explicit when-not-to-use instructions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JotaDeRodriguez/Bonsai_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server