Skip to main content
Glama
cad2revit-mcp

cad2revit-mcp

generate_revit_script

Converts component IR into deterministic Revit modeling instructions, handling family type mapping and level conversion for scripted BIM generation.

Instructions

把构件IR转换为确定性建模指令集,完成族类型映射与标高换算。

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

Input Schema

NameRequiredDescriptionDefault
task_idYes
level_mapNo
batch_sizeNo
family_mapNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the behavioral burden. It mentions deterministic output and mapping/conversion tasks, but omits whether it executes Revit, writes files, requires permissions, or has side effects.

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 description is a single front-loaded sentence with no filler. Every phrase contributes to the stated purpose, and the terseness is not itself a structural flaw.

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 tool has moderate complexity: four parameters, no annotations, and 0% schema description coverage, though an output schema exists. The description covers the core transformation but leaves parameter usage, prerequisites, and execution boundaries unexplained.

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?

Schema coverage is 0% for four parameters, so the description must compensate. It alludes to family_map and level_map via “family type mapping” and “level conversion,” but does not explain task_id, batch_size, or any expected formats or meanings.

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?

States a specific transformation: converting component IR into a deterministic modeling instruction set, with family type mapping and level conversion. It identifies the resource and operation clearly, but does not differentiate itself from siblings such as run_revit_script.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

Provides no explicit when-to-use or when-not-to-use guidance, and names no alternative sibling. The purpose implies a generation step after component IR exists, but the agent must infer that context.

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