Skip to main content
Glama
cad2revit-mcp

cad2revit-mcp

run_revit_script

Runs Revit modeling tasks in batches on local Revit, validates changes with dry-run mode, and rolls back failed batches to keep BIM models consistent.

Instructions

在本地Revit按批次建模;dry_run只校验,失败批次整批回滚。

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": {
      "task_id": "<task_id>"
    },
    "name": "run_revit_script"
  }
}

Input Schema

NameRequiredDescriptionDefault
resumeNo
dry_runNo
task_idYes
autosave_snapshotNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral-disclosure burden and usefully reveals local batch execution, validation-only dry runs, and rollback of an entire failed batch. It leaves other important behavior unspecified, including what resume and autosave_snapshot do, whether successful batches remain committed, and what local Revit prerequisites or side effects apply.

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?

The single compact sentence front-loads the action and environment, then adds two high-value execution qualifiers without redundancy. Its brevity contributes to omissions, but those are assessed under the other dimensions rather than as wasted or poorly structured wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema removes the need to describe return values, and the dry-run and rollback details cover important safety behavior. For a local mutation tool with no annotations and four otherwise undocumented parameters, however, the missing task prerequisites, resume and snapshot semantics, and workflow relationship to sibling tools leave substantial invocation gaps.

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

Parameters2/5

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

Only dry_run receives meaning beyond its bare schema name and default: it validates without modeling. Despite 0% schema description coverage, task_id, resume, and autosave_snapshot remain unexplained, so the agent cannot determine where the task ID comes from or precisely how the two default-enabled behaviors work.

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?

The description clearly states that the tool performs batch modeling in a local Revit instance, providing a concrete action, resource, and environment. It does not explicitly distinguish this execution/modeling step from siblings such as generate_revit_script or check_model.

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?

The statement that dry_run only performs validation gives useful guidance about the available validation mode. However, the description does not explain when to use validation versus actual modeling, what prerequisites task_id implies, or when this tool should be used relative to script generation or model-checking siblings.

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