Skip to main content
Glama
Boti-Ormandi

archicad-mcp

by Boti-Ormandi

get_docs

Browse, search, and retrieve full documentation for Archicad commands. Use categories, keywords, or exact command names to find schemas and examples.

Instructions

Get documentation for Archicad commands.

USAGE: get_docs() # Overview: categories with counts get_docs(category="Element Commands") # Browse: commands in a category get_docs(search="...") # Find commands by keyword get_docs(command="CommandName") # Full schema for one command get_docs(commands=["A", "B"]) # Full schemas for multiple

DISCOVERY WORKFLOW:

  1. get_docs() -> see categories

  2. get_docs(category="...") -> see command names

  3. get_docs(command="...") -> full schema

SEARCH FEATURES:

  • Searches across: names, descriptions, parameters, examples, notes

  • Element types: "wall" -> suggests GetElementsByType(elementType="Wall")

  • Partial match: "prop" finds property commands

  • Typo tolerant: "proprty" -> property commands

  • Multi-word: "create slab" finds CreateSlabs

Args: search: Search query (e.g., "wall", "create slab", "property") command: Exact command name for full schema commands: List of command names for full schemas category: Category name to list all commands in it

Examples: get_docs() # Overview get_docs(category="Element Commands") # Browse category get_docs(search="wall") # Commands for walls get_docs(search="create") # Creation commands get_docs(command="CreateSlabs") # Full schema for CreateSlabs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchNo
commandNo
commandsNo
categoryNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations, so description carries full burden. It describes behavior: returns categories, commands, or full schemas, and includes search features (typo tolerance, partial match). It does not mention rate limits or authentication, but as a read-only documentation tool, these are less critical. Could be more precise about output structure, but overall transparent.

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?

Well-structured with sections for usage, discovery workflow, search features, args, and examples. Front-loaded purpose. Slightly long but every section adds value; minor redundancy in examples.

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 discovery workflow, search features, and all parameter use cases. Has output schema so no need to explain return format in detail. Given complexity, description is complete and self-contained.

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?

Schema coverage is 0%, but description compensates fully: explains each parameter's purpose, provides multiple examples, and details search features (typo tolerance, multi-word). Adds significant meaning beyond the bare schema.

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?

Clearly states it provides documentation for Archicad commands. The description distinguishes it from sibling tools (execute_script, get_properties, list_instances) by focusing on documentation retrieval rather than execution or property listing.

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?

Provides explicit usage patterns (with and without arguments) and a discovery workflow. It also describes search features. However, it does not explicitly state when not to use this tool (e.g., when needing to execute commands instead of reading docs), which would further enhance clarity.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Boti-Ormandi/archicad-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server