Skip to main content
Glama

get_selected_ifc_entities

Extract IFC building model data from manually selected objects in Blender for focused analysis and manipulation.

Instructions

Get IFC entities corresponding to the currently selected objects in Blender.
This allows working specifically with objects the user has manually selected in the Blender UI.

Returns:
    A JSON-formatted string with information about the selected IFC entities

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler function that proxies the 'get_selected_ifc_entities' command to the Blender addon via socket connection, receives the result, formats it as JSON string, and handles errors. This is the primary implementation of the tool in the MCP server.
    @mcp.tool()
    def get_selected_ifc_entities() -> str:
        """
        Get IFC entities corresponding to the currently selected objects in Blender.
        This allows working specifically with objects the user has manually selected in the Blender UI.
        
        Returns:
            A JSON-formatted string with information about the selected IFC entities
        """
        try:
            blender = get_blender_connection()
            result = blender.send_command("get_selected_ifc_entities")
            
            # Return the formatted JSON of the results
            return json.dumps(result, indent=2)
        except Exception as e:
            logger.error(f"Error getting selected IFC entities: {str(e)}")
            return f"Error getting selected IFC entities: {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 that the tool retrieves data (implied read-only) and specifies the return format ('JSON-formatted string'), but lacks details on permissions, error handling, or rate limits, which are important for a tool interacting with Blender selections.

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 in the first sentence, followed by usage context and return format in two additional sentences. Every sentence adds value without redundancy, making it efficiently structured and easy to parse.

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 the tool's moderate complexity (interfacing with Blender selections and IFC data), no annotations, and no output schema, the description is adequate but incomplete. It explains what the tool does and the return format, but lacks details on output structure, error cases, or prerequisites like Blender being in a specific state.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately does not discuss parameters, focusing instead on the tool's purpose and output, which aligns with the baseline expectation for zero-parameter tools.

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 specific action ('Get IFC entities') and the target resource ('currently selected objects in Blender'), distinguishing it from siblings like 'list_ifc_entities' or 'get_ifc_properties' by focusing on user-selected objects rather than all entities or specific properties.

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?

It provides clear context for when to use this tool ('working specifically with objects the user has manually selected in the Blender UI'), but does not explicitly mention when not to use it or name alternatives like 'list_ifc_entities' for non-selected objects.

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