Skip to main content
Glama
Sign In
Archicad MCP Connector

Archicad MCP Connector

by davidharutyunyan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Delete attributes

delete_attributes
Destructive

Delete Archicad attributes of one type in a single undo step; Archicad reassigns affected elements, and layers holding elements are refused unless force is enabled.

Instructions

Deletes attributes of one type (one undo step). Archicad reassigns elements that used a deleted attribute (check them afterwards). WARNING: deleting a LAYER deletes every element on it — the tool refuses layers that still hold elements unless force: true (move elements with modify_elements first). Pens, fonts, the Archicad layer and some built-in attributes (the last one of a type, Solid/Empty fills, line type 1) cannot be deleted. Returns {results: [{index, name, deleted: true} | {error}]}.

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": {
      "type": "<type>",
      "attributes": "<attributes>"
    },
    "name": "delete_attributes"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesAttribute type (pens and fonts cannot be deleted)
forceNoLayers only: also delete layers that still hold elements (the elements are deleted too)
undoNameNo
attributesYesAttributes to delete: names (localized), indices or {guid}

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare destructive/non-idempotent; the description adds the deeper traits that matter: single undo step, automatic reassignment of elements using a deleted attribute, the full cascade when deleting a layer, and the refusal semantics. This is genuinely additive context beyond the structured hints.

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?

Purpose is front-loaded, the destructive warning is capitalized and prominent, and the return shape closes the definition. It is dense and slightly run-on, but every sentence carries operational information rather than filler.

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 destructive, multi-param tool with no output schema, it covers the return format inline, the refusal conditions, the force override, and the post-deletion side effects. An agent has everything needed to call it safely without further lookup.

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 75% and already documents type and force, so the baseline is 3. The description goes further by tying force to the layer cascade and the modify_elements remediation, and by naming the accepted attribute identifiers (name/index/guid). Only undoName receives no explanation anywhere.

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 ('Deletes attributes of one type') and immediately scopes it ('one undo step'). An agent can distinguish this from sibling element deletions like delete_elements or delete_stories without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use for force ('layers that still hold elements'), the precondition to satisfy first ('move elements with modify_elements'), and the exclusion set (pens, fonts, Archicad layer, last-of-type, Solid/Empty fills, line type 1). Alternative routing is spelled out rather than inferred.

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