Skip to main content
Glama
Archicad-MCP

Archicad-MCP

by alesdev88

Replace current selection

set_selection

Replace the current selection with the given element GUIDs. Whatever the user had selected by hand is deselected. The selection is read back afterwards.

Instructions

Replace the current selection with the given element GUIDs. Whatever the user had selected by hand is deselected. The selection is read back afterwards. Returns requested; selected, the count Archicad really selected (it answers success and still leaves some unselected: section Objects, railing sub-elements, elevation marker parts, or GUIDs not in the plan); not_selected with those GUIDs when any; and the coverage of the read, as get_selection.

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": {
      "guids": "<guids>"
    },
    "name": "set_selection"
  }
}

Input Schema

NameRequiredDescriptionDefault
portNo
guidsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations by warning that the user's hand-made selection is deselected, and by disclosing partial-success behavior — Archicad can answer success while silently skipping certain Objects, railing sub-elements, elevation marker parts, or GUIDs not in the plan. That is exactly the operational hazard an agent needs.

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?

The core action and the destructive effect on the existing selection are front-loaded. The return-value sentence is long and runs together several distinct outcomes, but nearly every clause carries useful information.

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?

An output schema exists, yet the description still usefully explains the 'requested / selected / not_selected / coverage' shape and the mismatch cases. The only gap for a two-parameter mutation tool is the unaddressed 'port' parameter.

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 0%, so the description must carry the load. It explains 'guids' concretely (element GUIDs, must be in the plan) but says nothing about the optional 'port' parameter, leaving one of two parameters undocumented in both schema and prose.

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: 'Replace the current selection with the given element GUIDs.' The name, title and first sentence agree, and the verb 'replace' clearly differentiates it from get_selection and clear_selection in the sibling list.

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 implied by the semantics (set an exact selection), but the description never says when to prefer this over get_selection or clear_selection, nor any prerequisite such as needing elements to have been found first. An agent must infer the workflow.

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