Skip to main content
Glama

How to get IFC4 (BIM) and FBX

how_to_get_bim
Read-onlyIdempotent

Guides you to the Download IFC (BIM) and FBX buttons, explains what each file contains, and tells when the 1:1 ceiling drawing opens; add a catalogue code for composition status.

Instructions

Step-by-step: where the "Download IFC (BIM)" and "Download FBX (3ds Max)" buttons are (step "3D composition scheme" → "Documents" drawer), what the IFC4 and FBX files contain and what they do not (no textures/UV, BIM properties only in IFC4, ceiling fixing points as IfcDiscreteAccessory objects), and when the 1:1 ceiling drawing opens (only after the production brief is started in production). With a code, the answer starts with the status of that composition (full calculation / calculated individually; ribbon, chain, frame, ready scene). Text in English or Russian.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "how_to_get_bim"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNoOptional catalogue code to prefix the guide with that composition's status
langNoen (default) or ru

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, openWorldHint=false, and idempotentHint=true. The description adds substantive context beyond the annotations: no textures/UV, BIM properties only in IFC4, ceiling fixing points as IfcDiscreteAccessory objects, and the 1:1 drawing opening only after the production brief is started. It does not mention auth or rate limits, but those are minor for a read-only guide.

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 front-loaded with 'Step-by-step' and packs the necessary guide content into three sentences. Parenthetical lists and status examples make it dense but not wasteful; minor run-on quality keeps it from a 5.

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

Completeness5/5

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

For a guide tool with no output schema, the description explains what the answer covers: button locations, file contents and limitations, drawing availability, how the optional code affects the answer, and language output. It is complete enough for an agent to invoke correctly.

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?

Schema coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema for code: when supplied, the answer is prefixed with that composition's status, and it enumerates status categories such as full calculation/calculated individually and ribbon/chain/frame/ready scene.

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 states a specific instructional purpose: step-by-step guidance for locating the IFC4/BIM and FBX download buttons, explaining what those files contain, and when the 1:1 ceiling drawing opens. It is clearly a how-to guide, distinguishable from sibling data-retrieval tools such as get_composition or search_compositions.

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 gives clear context for use: questions about downloading IFC/FBX files, file contents, and ceiling drawing availability. It also notes that an optional code changes the answer, but it does not explicitly exclude other uses or name sibling alternatives.

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