Skip to main content
Glama
flinker-app

ifc-mcp

by flinker-app
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

set BCF view

set-bcf-view

Set an open IFC viewer's view state by applying a BCF/BCFZIP viewpoint from a local path or generated download URL.

Instructions

Set the view state in the already-open local IFC viewer by applying a BCF/BCFZIP viewpoint file. Pass either a local BCF/BCFZIP file path or a generated BCF download URL from run Python saved_files. This tool does not show/load IFC files; use show-ifc-file for that. It should not open a new browser tab and should not use browser automation. To generate a BCFZIP with run-python, write a .bcfzip file, then call set-bcf-view with saved_files[0].url:

from uuid import uuid4
import ifcopenshell
from bcf.v3 import model as mdl
from bcf.v3.bcfxml import BcfXml
from bcf.v3.visinfo import VisualizationInfoHandler

model = ifcopenshell.open("sample.ifc")
gid = model.by_type("IfcWall")[0].GlobalId
component = mdl.Component(ifc_guid=gid)
visinfo = mdl.VisualizationInfo(
    guid=str(uuid4()),
    components=mdl.Components(
        selection=mdl.ComponentSelection(component=[component]),
        visibility=mdl.ComponentVisibility(
            default_visibility=False,
            exceptions=mdl.ComponentVisibilityExceptions(component=[component]),
        ),
    ),
)
bcf = BcfXml.create_new(project_name="IFC MCP")
topic = bcf.add_topic("Review wall", "Review wall", "ifc-mcp", topic_type="Issue", topic_status="Open")
topic.add_visinfo_handler(VisualizationInfoHandler(visinfo))
bcf_path = "view.bcfzip"
bcf.save(bcf_path)
print(str(bcf_path))

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bcf_pathYesLocal BCF/BCFZIP file path, or a generated BCF download URL from run Python saved_files, to apply in the viewer.

Tool Definition Quality

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It discloses key behaviors: it only sets view state in an already-open viewer, does not show/load IFC files, should not open a new tab, and should not use browser automation. It also implies a prerequisite (viewer must be open). However, it does not mention return values or error handling, which would contribute to full transparency.

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 core description is concise and front-loaded, with the first sentence stating purpose and the next clarifying input. The long code example earns its place by showing a complete workflow, but it adds length. Overall, it is well-structured and not wasteful, though it could be slightly tighter without losing value.

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 simple schema (one param, no output schema) and lack of annotations, the description provides adequate context: purpose, input types, exclusions, and a full usage example. It even gives a Python code sample for generating the BCFZIP. However, it stops short of explaining the tool's return value or potential errors, which is a minor gap for an otherwise clear description.

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

Parameters3/5

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

Schema description coverage is 100% for the single parameter, so the baseline is 3. The description repeats the same information about accepting a local path or generated URL, but adds little beyond the schema description. The code example illustrates usage but does not substantially enhance parameter understanding beyond what the schema already provides.

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 function: 'Set the view state in the already-open local IFC viewer by applying a BCF/BCFZIP viewpoint file.' It uses a specific verb ('set'), identifies the resource ('view state in viewer'), and explicitly distinguishes from siblings by stating 'This tool does not show/load IFC files; use show-ifc-file for that.'

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

Usage Guidelines5/5

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

Provides explicit when-to-use and when-not-to-use guidance: it says not to use for showing/loading IFC files and points to show-ifc-file as the alternative. It also explains a workflow with run-python to generate the BCFZIP and how to pass the URL, giving clear context for when this tool is appropriate.

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/flinker-app/ifc-mcp'

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