Skip to main content
Glama

get_ifc_properties

Extract properties from IFC building model entities in Blender, either by GlobalId or from selected objects, returning structured JSON data for analysis.

Instructions

Get properties of IFC entities. Can be used to get properties of a specific entity by GlobalId,
or to get properties of all currently selected objects in Blender.

Args:
    global_id: GlobalId of a specific IFC entity (optional if selected_only is True)
    selected_only: If True, return properties for all selected objects instead of a specific entity

Returns:
    A JSON-formatted string with entity information and properties

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
global_idNo
selected_onlyNo

Implementation Reference

  • The main handler function for the MCP tool 'get_ifc_properties'. It validates input parameters, establishes a connection to the Blender addon via socket, forwards the command with parameters to Blender, and returns the JSON-formatted response or an error message.
    def get_ifc_properties(global_id: str | None = None, selected_only: bool = False) -> str:
        """
        Get properties of IFC entities. Can be used to get properties of a specific entity by GlobalId,
        or to get properties of all currently selected objects in Blender.
        
        Args:
            global_id: GlobalId of a specific IFC entity (optional if selected_only is True)
            selected_only: If True, return properties for all selected objects instead of a specific entity
        
        Returns:
            A JSON-formatted string with entity information and properties
        """
        try:
            blender = get_blender_connection()
            
            # Validate parameters
            if not global_id and not selected_only:
                return json.dumps({"error": "Either global_id or selected_only must be specified"}, indent=2)
            
            result = blender.send_command("get_ifc_properties", {
                "global_id": global_id,
                "selected_only": selected_only
            })
            
            # Return the formatted JSON of the results
            return json.dumps(result, indent=2)
        except Exception as e:
            logger.error(f"Error getting IFC properties: {str(e)}")
            return f"Error getting IFC properties: {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. It discloses the tool's dual behavior modes and output format (JSON-formatted string), but lacks details on permissions, rate limits, error conditions, or whether it's read-only (implied by 'Get' but not explicit). It adequately describes what the tool does but misses some behavioral traits.

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

Conciseness5/5

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

The description is front-loaded with the core purpose, followed by clear sections for Args and Returns. Every sentence earns its place: no redundancy, and the structure (purpose, parameters, return) is logical and efficient for quick understanding.

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

Completeness3/5

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

Given 2 parameters with 0% schema coverage and no output schema, the description provides adequate basics (purpose, parameters, return format) but lacks depth. It doesn't explain the JSON structure, error handling, or dependencies (e.g., Blender context), leaving gaps for a tool with moderate complexity and no annotations.

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 schema description coverage is 0%, so the description must compensate. It adds meaningful semantics: explaining that global_id is optional when selected_only is True, clarifying that selected_only returns properties for all selected objects, and indicating the mutual exclusivity between the two parameters. This goes beyond the bare schema, though it could detail parameter formats or constraints more.

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 verb 'Get' and resource 'properties of IFC entities', specifying two distinct modes: by GlobalId or for selected Blender objects. It distinguishes itself from siblings like 'get_ifc_quantities' or 'get_ifc_relationships' by focusing on properties rather than other entity attributes.

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 each mode (by GlobalId vs. selected objects) and mentions the optional nature of global_id when selected_only is True. However, it doesn't explicitly state when to choose this tool over similar siblings like 'get_selected_ifc_entities' or 'list_ifc_entities', which might offer overlapping functionality.

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