Skip to main content
Glama
alesdev88

Archicad-MCP

by alesdev88

Create Swept Beam

create_swept_beam
Destructive

Place or update a sloped, curved beam in Archicad from a Morph line, polyline, line, arc, or point list, with profile, slope, offsets, and end cuts; dry-run by default.

Instructions

Place a Swept Beam: a sloped, curved beam with a Profile Manager profile or a rectangle, as the 'Swept Beam' library part. The path comes from source_guid (a Morph line, Polyline, Line or Arc) or from points [{x, y, z}] in metres. Flat sources take start_height (metres above the source) and slope_percent; morph lines and points keep their own heights. profile is {"attribute": ""} or {"rectangle": {"width", "height", "building_material"}} (default 0.2 x 0.2 rectangle). update_guid rewrites the path of an existing Swept Beam, keeping its GUID; its profile, offsets, flip and end cuts stay unless given, and node roll resets to 0. End cuts in degrees: cut_start_plan and cut_end_plan turn a cut counter-clockwise from square in plan (-80 to 80); cut_start_tilt and cut_end_tilt lean the top of the face out past the end (-85 to 85, 0 is square to the beam, the beam's slope there gives a vertical face). ref_line ('left face', 'centre', 'right face', looking from the first point to the last) puts that face of the beam on the path; ref_offset (metres) moves the beam that far away from it (with centre, to the right). DRY-RUN BY DEFAULT: reports nodes, arcs, the maximum deviation from the source and warnings. Pass dry_run=false to place or update.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
flipNo
portNo
pointsNo
dry_runNo
profileNo
offset_uNo
offset_wNo
ref_lineNo
ref_offsetNo
source_guidNo
update_guidNo
cut_end_planNo
cut_end_tiltNo
start_heightNo
slope_percentNo
cut_start_planNo
cut_start_tiltNo
path_toleranceNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.1

TDQS

A4.7/5.0
Behavior5/5

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

Despite annotations already flagging destructiveHint, the description adds substantial behavior: dry-run is the default, update_guid preserves the GUID while profile/offsets/flip/end cuts stay unless specified, node roll resets to 0, and cut angles have documented ranges and directional meaning. This is unusually rich disclosure for a mutation tool.

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?

Dense but front-loaded, opening with the object and path sources before drilling into profile, update, cuts and reference-line options. The single long block is justified by 18 parameters, though slightly better structuring would aid scanning.

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 complex 18-parameter mutation tool with an output schema available, the description covers construction logic, update semantics, units, ranges and the dry-run report contents. An agent has everything needed to call it correctly without opening the schema.

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

Parameters5/5

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

Schema coverage is 0%, so the description carries the full burden and mostly succeeds: it gives units (metres, degrees), ranges (-80 to 80, -85 to 85), defaults (0.2 x 0.2 rectangle), and meaning for source_guid, points, start_height, slope_percent, profile, update_guid, ref_line, ref_offset, and all four cut parameters. Only path_tolerance, port and the offset_u/offset_w pair are left undefined, which is a minor gap given the breadth covered.

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?

States a specific verb and resource ('Place a Swept Beam') and immediately defines what the object is (sloped, curved beam with a profile or rectangle) and which library part it becomes. Distinguishes itself from generic siblings like create_elements by naming the exact BIM construct.

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?

Explains when to use which path source (flat source with start_height/slope_percent vs morph lines/points keeping their own heights) and how update_guid converts the call into an update of an existing beam. It lacks explicit routing to alternative sibling tools, but the create-vs-update split is clear.

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