Skip to main content
Glama
tapir-archicad-mcp

tapir-archicad-mcp

by SzamosiMate

Get or List Archicad Jobs

archicad_get_job
Read-onlyIdempotent

Checks Archicad job status by handle, waits briefly for completion, or lists recent jobs when no handle is given to recover lost responses before retrying writes.

Instructions

With no job_handle, immediately lists all retained executions newest first, including fast, completed, and failed jobs, with command, port, timestamps, and a short argumentsPreview. Use this to recover after a lost response before retrying a write; similar calls may be ambiguous. With a job_handle, waits up to the configured threshold and returns running, completed with result, or failed with error. Polling never redispatches commands.

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": "archicad_get_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_handleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.5

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), but the description adds genuinely new behavioral facts: newest-first ordering, wait-up-to-threshold semantics, the running/completed/failed result states, the argumentsPreview field, and the key guarantee that 'polling never redispatches commands.' That last point is exactly the kind of side-effect disclosure 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?

Three dense sentences, front-loaded with the no-argument behavior, and every clause adds information (ordering, result states, no-redispatch guarantee). Slightly packed for one breath, but there is no 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?

With no output schema, the description must describe returns, and it does: command, port, timestamps, argumentsPreview for the list mode and running/completed-with-result/failed-with-error for the wait mode. Combined with the annotation-covered safety profile, an agent has everything needed to call this correctly.

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 0% and the single parameter has no description, so the description carries the burden and does so well: it explains that omitting job_handle triggers listing and supplying it triggers a blocking wait. It does not clarify the accepted handle format or where a handle is obtained, so it falls just short of full compensation.

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?

The description states a precise dual behavior: with no job_handle it lists retained executions, with a job_handle it waits for and returns that job's outcome. This unambiguously separates it from write-oriented siblings like archicad_call_tool and from discovery tools, and an agent can pick the correct mode 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 Guidelines4/5

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

It gives explicit when-to-use guidance ('use this to recover after a lost response before retrying a write') and a caution that 'similar calls may be ambiguous.' It stops short of naming an alternative sibling tool for retry decisions, so it is clear but not a full when/when-not/alternatives statement.

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