Skip to main content
Glama
Archicad MCP Connector

Archicad MCP Connector

Create railings

create_railings

Creates railings along a line or path, including curved stair boundaries, with height, offset, and story controls in one undo step.

Instructions

Creates railings in one undo step along a reference line: 'begin'/'end' or a 'path' polyline (points may carry z to follow a slope; add arcs for curves) with the Railing tool's default posts/rails/panels. Set 'height', 'bottomOffset' and the reference line side. Coordinates in meters, angles in degrees, on the given story (default: current story); unspecified settings come from the tool defaults. Tip: to guard a stair, use its leftBoundary/rightBoundary from get_element_details as the path. Returns [{guid, type} | {error}]; get_element_details lists the segments and the GUIDs of posts, rails, handrails, panels and balusters.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "railings": "<railings>"
    },
    "name": "create_railings"
  }
}

Input Schema

NameRequiredDescriptionDefault
railingsYesRailings to create
undoNameNoName of the undo step shown in Archicad

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description discloses that creation happens 'in one undo step', that unspecified settings inherit the Railing tool defaults, that the story defaults to the current story, and the error/return shape. This is substantive behavioral context.

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, leading with the core verb and geometry, then parameters, then a tip and return value. Slightly long as a single block, but nearly every clause earns its place.

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?

No output schema exists, yet the description explains the return value ([{guid, type} | {error}]) and points to get_element_details for sub-element GUIDs. Combined with units, undo semantics, and default-inheritance behavior, it is complete enough for correct invocation.

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, but the description adds real semantics: coordinates in meters, angles in degrees, z carrying slope, arcs for curves, closing a railing by repeating the first point, and the meaning of height/bottomOffset/reference line side. It lifts parameter meaning above the schema text.

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 ('Creates') and resource ('railings') and immediately scopes it to a reference line, distinguishing it from modify_railings and create_stairs in the sibling list. An agent knows exactly what geometry it produces.

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?

Gives a concrete routing tip (use a stair's leftBoundary/rightBoundary from get_element_details as the path to guard a stair) and explains the begin/end vs path choice. It does not explicitly state when NOT to use it (e.g. use modify_railings for existing railings), so it falls short of full 5.

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

Deploy Server

Other Tools