Skip to main content
Glama
Sign In
Archicad MCP Connector

Archicad MCP Connector

by davidharutyunyan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Modify roofs

modify_roofs
DestructiveIdempotent

Modify existing roofs (SinglePlane/MultiPlane) in Archicad by updating specified fields like geometry, slope, and surfaces while keeping others unchanged. Batch changes in one undo step.

Instructions

Changes existing roofs (the class SinglePlane/MultiPlane cannot change). SinglePlane: polygon, pivotLine, slopeAngle, risesToLeft, edges. MultiPlane: pivotPolygon, slopeAngle, levels, eavesOverhang, pivotEdges (per-plane pitch / gable end / overhang; edge indices of the stored pivot polygon as returned by get_element_details). Both: level, thickness, structure, surfaces, edge trim, floor plan attributes. Fields as in create_roofs. Only the given fields change; the others keep their values. Each item must be an element of this type (checked first; other items still run). Returns [{guid} | {error}] in input order, one undo step.

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": {
      "roofs": "<roofs>"
    },
    "name": "modify_roofs"
  }
}

Input Schema

NameRequiredDescriptionDefault
roofsYesPatches {guid, ...fields to change}
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?

Annotations declare destructive/idempotent/not-readonly, and the description goes well beyond them: partial-update semantics, per-item type validation with 'other items still run' error isolation, return shape [{guid} | {error}] in input order, and a single undo step. This is exactly the behavioral context an agent needs for a batch mutation.

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?

Single dense paragraph, purpose front-loaded in the first clause, no filler sentences. It is long, but proportionate to an enormous schema and a class-scoped tool; the density is justified rather than padded.

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 very complex mutation tool with 100% schema coverage and no output schema, the description covers class-specific fields, patch semantics, validation behavior, error/return handling, and undo scoping. Nothing an agent needs to call it correctly 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?

Schema coverage is 100%, so the schema already documents every field. The description still adds non-derivable meaning: which fields belong to which roof class, that edge indices refer to the stored pivot polygon 'as returned by get_element_details', and that field syntax matches create_roofs.

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+resource ('Changes existing roofs') and immediately distinguishes behavior by class (SinglePlane vs MultiPlane fields), plus names the create_roofs sibling as the field reference. An agent can tell this apart from create_roofs and modify_elements without opening a 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?

Clearly conveys patch semantics ('Only the given fields change; the others keep their values') and preconditions ('Each item must be an element of this type'). It does not explicitly say when to prefer this over create_roofs or the generic modify_elements, but the context is clear enough to select the tool.

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