Skip to main content
Glama

georeference_ifc_model

Assign geographic coordinates to IFC building models by creating or updating coordinate reference systems and map conversions for accurate location positioning.

Instructions

Georeferences the IFC currently opened in Bonsai/BlenderBIM by creating or updating IfcProjectedCRS and IfcMapConversion. Optionally updates IfcSite and writes the file to disk.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
crs_modeYes
epsgNo
crs_nameNo
geodetic_datumNo
map_projectionNo
map_zoneNo
eastingsNo
northingsNo
orthogonal_heightNo
scaleNo
x_axis_abscissaNo
x_axis_ordinateNo
true_north_azimuth_degNo
context_filterNoModel
context_indexNo
site_ref_latitudeNo
site_ref_longitudeNo
site_ref_elevationNo
site_ref_latitude_ddNo
site_ref_longitude_ddNo
overwriteNo
dry_runNo
write_pathNo

Implementation Reference

  • The handler function for the 'georeference_ifc_model' tool. It collects georeferencing parameters, filters out None values, and forwards them as a command to the Blender addon via the socket connection for actual IFC model georeferencing.
    def georeference_ifc_model(
        crs_mode: str,
        epsg: int = None,
        crs_name: str = None,
        geodetic_datum: str = None,
        map_projection: str = None,
        map_zone: str = None,
        eastings: float = None,
        northings: float = None,
        orthogonal_height: float = 0.0,
        scale: float = 1.0,
        x_axis_abscissa: float = None,
        x_axis_ordinate: float = None,
        true_north_azimuth_deg: float = None,
        context_filter: str = "Model",
        context_index: int = None,
        site_ref_latitude: list = None,      # [deg, min, sec, millionth]
        site_ref_longitude: list = None,     # [deg, min, sec, millionth]
        site_ref_elevation: float = None,
        site_ref_latitude_dd: float = None,  # Decimal degrees (optional)
        site_ref_longitude_dd: float = None, # Decimal degrees (optional)
        overwrite: bool = False,
        dry_run: bool = False,
        write_path: str = None,
    ) -> str:
        """
        Georeferences the IFC currently opened in Bonsai/BlenderBIM by creating or 
        updating IfcProjectedCRS and IfcMapConversion. Optionally updates IfcSite 
        and writes the file to disk.
        """
        import json
        blender = get_blender_connection()
    
        # Build params excluding None values to keep the payload clean
        params = {
            "crs_mode": crs_mode,
            "epsg": epsg,
            "crs_name": crs_name,
            "geodetic_datum": geodetic_datum,
            "map_projection": map_projection,
            "map_zone": map_zone,
            "eastings": eastings,
            "northings": northings,
            "orthogonal_height": orthogonal_height,
            "scale": scale,
            "x_axis_abscissa": x_axis_abscissa,
            "x_axis_ordinate": x_axis_ordinate,
            "true_north_azimuth_deg": true_north_azimuth_deg,
            "context_filter": context_filter,
            "context_index": context_index,
            "site_ref_latitude": site_ref_latitude,
            "site_ref_longitude": site_ref_longitude,
            "site_ref_elevation": site_ref_elevation,
            "site_ref_latitude_dd": site_ref_latitude_dd,
            "site_ref_longitude_dd": site_ref_longitude_dd,
            "overwrite": overwrite,
            "dry_run": dry_run,
            "write_path": write_path,
        }
        params = {k: v for k, v in params.items() if v is not None}
    
        try:
            result = blender.send_command("georeference_ifc_model", params)
            return json.dumps(result, ensure_ascii=False, indent=2)
        except Exception as e:
            logger.exception("georeference_ifc_model error")
            return json.dumps(
                {"success": False, "error": "Could not georeference the model.", "details": str(e)},
                ensure_ascii=False,
                indent=2,
            )
Behavior2/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 mentions the tool creates/updates objects and optionally updates IfcSite and writes to disk, indicating it's a mutation/write operation. However, it lacks critical behavioral details: what permissions are needed, whether changes are reversible, what happens if the file isn't saved, error conditions, or performance characteristics. For a complex 23-parameter mutation tool, this is a significant gap.

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 appropriately concise at three sentences. It's front-loaded with the core purpose, followed by optional behaviors. No wasted words, though it could be slightly more structured (e.g., bullet points for optional features). Every sentence adds value: the first states the main action, the second adds optional site updates, and the third clarifies file writing.

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

Completeness2/5

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

Given the high complexity (23 parameters, mutation operation), lack of annotations, 0% schema description coverage, and no output schema, the description is incomplete. It doesn't explain what the tool returns (success/failure, updated objects, file path), doesn't detail parameter interactions (e.g., how crs_mode affects other params), and omits error handling. For a tool of this complexity, the description should provide much more contextual guidance.

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

Parameters2/5

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

Schema description coverage is 0%, so the schema provides only parameter names and types without explanations. The description mentions 'crs_mode' (implied by 'creating or updating IfcProjectedCRS'), 'epsg' (implied by georeferencing), and 'write_path' (implied by 'writes the file to disk'), but doesn't explain the purpose, relationships, or constraints of the 23 parameters. It fails to compensate for the complete lack of schema descriptions, leaving most parameters semantically opaque.

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

Purpose4/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: 'Georeferences the IFC currently opened in Bonsai/BlenderBIM by creating or updating IfcProjectedCRS and IfcMapConversion.' It specifies the verb ('georeferences'), resource ('IFC'), and target objects (IfcProjectedCRS, IfcMapConversion). However, it doesn't explicitly differentiate from siblings like 'get_ifc_georeferencing_info' (which likely reads rather than writes georeferencing data).

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

Usage Guidelines2/5

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

The description provides minimal usage guidance. It mentions the tool operates on 'the IFC currently opened in Bonsai/BlenderBIM,' which implies a prerequisite (an open IFC file), but doesn't specify when to use this tool versus alternatives like 'get_ifc_georeferencing_info' (for reading) or other geospatial tools. No explicit when-not-to-use or alternative recommendations are provided.

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