Skip to main content
Glama
ZedMoster

Revit MCP Server

by ZedMoster

link_dwg_and_activate_view

Link local DWG drawings to Revit projects and activate specific views for design coordination and documentation.

Instructions

链接本地 DWG 图纸并激活指定视图,遵循JSON-RPC 2.0规范。

特性:

  • 支持链接本地 DWG 图纸到当前项目

  • 支持激活指定视图

  • 自动验证参数有效性

  • 完善的错误处理机制

参数: ctx (Context): FastMCP上下文对象 method (str): JSON-RPC方法名,默认为"LinkDWGAndActivateView" params (List[Dict]): 参数列表,每个字典包含: - filePath (str): 本地 DWG 图纸路径 - viewName (str): 要激活的视图名称

返回: dict: JSON-RPC 2.0格式的响应,结构为: 成功时: { "jsonrpc": "2.0", "result": [ { "filePath": "链接的文件路径", "viewId": "视图ID", "viewName": "视图名称" }, ... ], "id": request_id } 失败时: { "jsonrpc": "2.0", "error": { "code": int, "message": str, "data": any }, "id": request_id }

示例: response = link_and_activate_view(ctx, params=[ {"filePath": "C:\Projects\SampleDrawing.dwg", "viewName": "Level 1"} ])

# 输出示例
{
    "jsonrpc": "2.0",
    "result": [
        {
            "filePath": "C:\Projects\SampleDrawing.dwg",
            "viewId": 123456,
            "viewName": "Level 1"
        }
    ],
    "id": 1
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
methodNoLinkDWGAndActivateView
paramsNo

Implementation Reference

  • The tool 'link_dwg_and_activate_view' is listed in GENERAL_TOOLS array, which is used for registration.
    GENERAL_TOOLS = [
        get_commands, execute_commands, call_func,
        find_elements, update_elements, delete_elements, parameter_elements, get_locations, move_elements,
        show_elements, active_view, get_selected_elements,
        link_dwg_and_activate_view, get_view_data
    ]
  • Registration loop that applies mcp.server.tool() decorator to link_dwg_and_activate_view and other general tools.
    for tool in GENERAL_TOOLS:
        server.tool()(tool)
  • Usage documentation in asset_creation_strategy prompt that describes when to use the tool.
    return """创建Revit模型元素时,请遵循以下策略和最佳实践:
    
    0. 在创建任何元素前,优先检查当前项目状态:
       - 使用get_commands()获取所有可用功能
       - 使用get_selected_elements()检查当前选中的元素
       - 使用find_elements()查找特定类别的现有元素
    
    1. 始终遵循正确的创建顺序:
       1. 基础参考系统
          - 使用create_levels()创建必要的标高
          - 使用create_grids()创建轴网系统
          - 使用create_floor_plan_views()为每个标高创建平面视图
    
       2. 主体结构元素
          - 使用create_walls()创建墙体,注意指定正确的起点、终点、高度和宽度
          - 使用create_floors()创建楼板,确保边界点形成封闭环路
    
       3. 二次构件
          - 使用create_door_windows()在墙体上创建门窗
            注意:门窗族需要指定宿主墙,所以必须先有墙再创建门窗
          - 使用get_locations()获取墙体的位置信息,以便正确放置门窗
    
       4. MEP系统
          - 使用create_ducts()创建风管
          - 使用create_pipes()创建管道
          - 使用create_cable_trays()创建电缆桥架
    
       5. 内部划分和标注
          - 使用create_rooms()在封闭区域创建房间
          - 使用create_room_tags()添加房间标签
    
       6. 文档整理
          - 使用create_sheets()创建图纸
          - 使用active_view()切换到需要的视图
          - 使用link_dwg_and_activate_view()链接DWG图纸
    
    2. 操作现有元素时的最佳实践:
       - 使用parameter_elements()获取元素参数,然后使用update_elements()修改
       - 使用move_elements()调整元素位置
       - 使用show_elements()在视图中高亮显示特定元素
       - 使用delete_elements()移除不需要的元素
    
    3. 创建复杂组件时:
       - 使用create_family_instances()创建参数化族实例
       - 对于未预定义的功能,使用call_func()调用特定功能
    
    4. 所有元素创建后的检查与验证:
       - 检查元素参数是否符合要求
       - 确保结构完整性和空间关系合理性
       - 使用show_elements()检查关键元素
       - 使用active_view()切换到需要的视图
    
    仅在以下情况使用原生RevitAPI:
    - 上述函数不能满足特定需求
    - 需要创建自定义参数或复杂约束
    - 需要进行高级计算或特殊几何操作
    - 需要与其他应用程序进行数据交换
    - 如果获取BuiltInCategory失败可以通过get_all_builtin_category查找
    """
  • Test file demonstrating the input parameters (filePath) and the corresponding RPC method name 'LinkDWGAndActivateView' likely called by the tool handler.
    data = [
        {
            "filePath": r"C:\Users\zed\AppData\Local\Autodesk\zedmoster\xmlRevitCopy\db991824-5d43-4a9a-9f2e-824e37abb87f.dwg",
        },
    ]
    
    # 构造 JSON-RPC 请求
    json_rpc_request = {
        "jsonrpc": "2.0",
        "method": "LinkDWGAndActivateView",
        "params": data,
    }
    
    # 发送更新元素数据
    send_tcp_data(json_rpc_request)
  • Import statement that brings in the tool handler functions including link_dwg_and_activate_view.
    from .tools import *
Behavior3/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It adds some useful context: mentions JSON-RPC 2.0 compliance, automatic parameter validation, and error handling mechanisms. However, it doesn't disclose important behavioral traits like whether this is a read-only or destructive operation, what permissions are required, or any rate limits. The description compensates somewhat but leaves significant gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is structured with sections (特性, 参数, 返回, 示例) but is overly verbose. It includes implementation details like JSON-RPC response structures and full example code that may not be necessary for an AI agent. The core purpose could be communicated more efficiently without sacrificing clarity.

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

Completeness3/5

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

Given no annotations, 0% schema coverage, and no output schema, the description provides moderate completeness. It documents parameters and return values in detail, which is good. However, for a tool that appears to perform both linking and activation operations (potentially complex mutations), it should provide more context about side effects, prerequisites, and error conditions to be fully complete.

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 description coverage is 0%, so the description must compensate. It provides detailed parameter documentation: explains that 'ctx' is a FastMCP context object, 'method' defaults to 'LinkDWGAndActivateView', and 'params' contains dictionaries with 'filePath' and 'viewName'. This adds substantial meaning beyond the bare schema. However, it doesn't fully document all parameter constraints or formats (e.g., what constitutes a valid filePath).

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 the tool's purpose: '链接本地 DWG 图纸并激活指定视图' (link local DWG drawings and activate specified views). It specifies both the action (link and activate) and the resource (DWG drawings and views). However, it doesn't explicitly differentiate from sibling tools like 'active_view' or 'create_floor_plan_views', which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. While it mentions JSON-RPC 2.0 compliance and lists features like automatic parameter validation and error handling, it doesn't specify scenarios where this tool is appropriate or when other tools (like 'active_view' for just activating views) should be used instead.

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/ZedMoster/revit-mcp'

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