Skip to main content
Glama
Sign In
Archicad-MCP

Archicad-MCP

by alesdev88
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Update this extension

update_extension
Destructive

Checks whether this extension has an available update, then with confirm=true downloads, verifies, and opens the installer for user approval; never downgrades or installs automatically.

Instructions

Update this extension to the newest release. Dry run by default: it compares the installed version with the latest release on GitHub and says what it would do. confirm=true downloads the bundle for this computer, checks its sha256 and opens it, so Claude Desktop shows its own install dialog; nothing is installed until the user accepts there. Never downgrades. Reaches GitHub only when called. A server not installed as a Claude Desktop bundle gets the upgrade command instead. Needs no running Archicad.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "update_extension"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.14.0

TDQS

A5/5.0
Behavior5/5

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

Goes far beyond the annotations: it discloses that the default is a non-mutating comparison, that confirm=true downloads and sha256-checks a bundle and opens an installer dialog, that nothing installs until user consent, that it never downgrades, and that it only touches the network when called.

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?

Dense but every sentence supplies new operational information, front-loaded with the default behavior and the mutation path; no filler or restatement of the title.

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?

Covers the mutation, the consent boundary, network behavior, downgrade policy, fallback path, and prerequisite (no running Archicad) — an agent has everything needed to call it safely, and return values are covered by the output schema.

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

Parameters5/5

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

With 0% schema description coverage, the description carries the full burden and does: it defines what confirm=true triggers step by step and what happens when it is omitted, which the bare boolean default of false would not convey.

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 and resource ('Update this extension to the newest release') and immediately clarifies the default behavior, so an agent knows exactly what the call does 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 Guidelines5/5

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

Explicitly distinguishes the dry-run case (default) from the real invocation (confirm=true) and gives an alternative path for servers not installed as a Claude Desktop bundle, which is the upgrade command.

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