Skip to main content
Glama
Sign In
Archicad MCP Connector

Archicad MCP Connector

by davidharutyunyan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Create skylights

create_skylights

Places roof skylights into Archicad roofs or shells in one undo step. Requires a host roof/shell GUID and plan point; size, library part, and parameters default to tool settings.

Instructions

Places skylights into roofs or shells (one undo step). Each skylight needs the host 'owner' (Roof or Shell GUID) and 'point' ({x,y}: plan position of its anchor on the roof). Size, library part and parameters default to the Skylight tool settings; library part names are LOCALIZED (search_library_parts, type Skylight). Returns [{guid, type} | {error}] in input order.

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": {
      "skylights": "<skylights>"
    },
    "name": "create_skylights"
  }
}

Input Schema

NameRequiredDescriptionDefault
skylightsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive mutation. The description adds value beyond them: "(one undo step)" discloses undo granularity, and the "[{guid, type} | {error}] in input order" clause reveals partial-failure semantics and per-item result ordering. It stops short of describing rollback behavior when some items fail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with purpose before prerequisites and return format. Every clause carries information (undo scope, required fields, defaulting, localization, result shape) with no filler.

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?

For a highly complex tool with a very rich nested schema and no output schema, the description covers the essentials: required fields, defaulting behavior, the localization caveat, and the return shape with error signaling. It could say more about how partial failures affect the whole batch, but nothing critical for invocation is missing.

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?

Top-level schema description coverage is 0% (the single 'skylights' array is undocumented), so the description carries real weight here: it explains that size, library part, and parameters fall back to the Skylight tool settings by default, and flags that library part names are LOCALIZED — a genuine gotcha not stated at the top level. It does not enumerate the many optional per-item fields, which the nested schema documents well.

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 names a specific verb and resource ("Places skylights into roofs or shells") and implicitly distinguishes this from siblings like create_roofs, create_shells, and create_openings by naming the host requirement. An agent can tell what this tool produces without opening the schema.

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 states the invocation prerequisites clearly (each skylight needs 'owner' as a Roof/Shell GUID and 'point' as a plan position), and routes the agent to search_library_parts for localized part names. There is no explicit when-not-to-use guidance or comparison against related creation tools, but the context is unambiguous.

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