Skip to main content
Glama
Sign In
Archicad MCP Connector

Archicad MCP Connector

by davidharutyunyan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Delete classification items

delete_classification_items
Destructive

Delete classification items and all their children in a single Archicad undo step, automatically unclassifying any elements that used them.

Instructions

Deletes classification items together with all their children in one undo step (elements classified with them become unclassified in that system). Returns {results: [{guid, id, deleted, deletedChildren} | {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": {
      "items": "<items>"
    },
    "name": "delete_classification_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes
systemNoSystem in which item IDs are looked up
undoNameNoName of the undo step shown in Archicad

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnly=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: cascading child deletion, side effect on classified elements, single-undo-step semantics, and the per-item result/error shape. It stops short of noting irreversibility or failure-partial-success behavior.

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?

Two sentences, front-loaded with the action and cascade scope, then the return shape. No filler. Slightly dense with parenthetical and inline object notation, but every clause earns its place.

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 destructive, non-idempotent mutation with annotations covering the safety profile, the description supplies cascade behavior, element side effects, undo grouping, and the return contract. The remaining gaps (partial-failure semantics, irreversibility, system-lookup implications) are minor.

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

Parameters3/5

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

Schema coverage is 67% and the schema itself documents items, system and undoName well. The description adds no parameter-level detail beyond the resource name, so the schema carries the load and the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Deletes classification items') and immediately qualifies scope with the cascade behavior ('together with all their children'). It does not explicitly distinguish itself from the sibling delete_classification_systems, but the resource noun is unambiguous.

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

Usage Guidelines3/5

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

Usage is only implied by the destructive semantics; there is no explicit when-to-use statement, no prerequisites, and no named alternative (e.g., modify_classification_items or delete_classification_systems). The note that classified elements become unclassified hints at the impact but not at when to prefer this 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