Skip to main content
Glama
ZedMoster

Revit MCP Server

by ZedMoster

move_elements

Move Revit elements in bulk by specifying distances in millimeters, with automatic unit conversion to feet and detailed feedback on moved elements.

Instructions

移动Revit元素,支持批量操作,遵循JSON-RPC 2.0规范。 mcp_tool使用时params不要有任何注释信息

特性:

  • 支持批量移动多个Revit元素

  • 自动处理单位转换(毫米转英尺)

  • 返回移动后的元素详细信息(使用ElementModelRequest格式)

  • 完善的错误处理机制

参数: ctx (Context): FastMCP上下文对象 method (str): JSON-RPC方法名,默认为"MoveElements" params (List[Dict]): 移动参数列表,每个字典包含: - elementId (str): 要移动的元素ID - x (float): X方向移动距离(毫米) - y (float): Y方向移动距离(毫米) - z (float): Z方向移动距离(毫米)

返回: dict: JSON-RPC 2.0格式的响应,结构为: 成功时: { "jsonrpc": "2.0", "result": [ { "elementId": "移动后的元素ID", "name": "元素名称", "familyName": "族名称" }, ... ], "id": request_id } 失败时: { "jsonrpc": "2.0", "error": { "code": int, "message": str, "data": any }, "id": request_id }

示例: response = move_elements(ctx, params=[ {"elementId": "123456", "x": 100, "y": 200, "z": 0}, {"elementId": "789012", "x": -50, "y": 0, "z": 300} ])

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
methodNoMoveElements
paramsNo

Implementation Reference

  • move_elements is included in GENERAL_TOOLS array, which lists functions to be registered as MCP tools.
    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
    ]
  • Loop that registers all functions in GENERAL_TOOLS, including move_elements, as MCP tools using server.tool() decorator.
    # 注册通用工具
    for tool in GENERAL_TOOLS:
  • Import statement that brings in move_elements and other tool functions from the .tools module.
    from .tools import *
  • Prompt documentation instructing users to use move_elements() to adjust element positions.
    - 使用move_elements()调整元素位置
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does well by describing key behaviors: batch operation support, automatic unit conversion (millimeters to feet), return format details (ElementModelRequest), and error handling mechanisms. However, it doesn't mention potential side effects (e.g., whether movement affects element relationships or properties), performance considerations for large batches, or authentication requirements.

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 well-structured with sections (特性, 参数, 返回, 示例), but it includes extraneous information. The note about 'mcp_tool使用时params不要有任何注释信息' is confusing and doesn't add value for tool selection. The JSON-RPC 2.0 compliance mention is repeated, and the example could be more concise. However, key information is front-loaded, and most sentences earn their place.

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

Completeness4/5

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

Given the complexity (a mutation tool with batch operations, unit conversion, and structured returns), no annotations, and no output schema, the description does a good job. It explains parameters thoroughly, describes return formats for both success and failure cases, and provides an example. The main gap is lack of sibling tool differentiation and minimal usage context, but it's largely complete for understanding the tool's operation.

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 description coverage is 0%, so the description must fully compensate. It does this excellently by detailing both parameters: 'method' (JSON-RPC method name, defaulting to 'MoveElements') and 'params' (a list of dictionaries with specific fields: elementId, x, y, z). It explains units (millimeters for distances), structure, and provides a clear example. This adds substantial 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?

The description clearly states the tool's purpose with a specific verb ('移动' meaning 'move') and resource ('Revit元素' meaning 'Revit elements'), distinguishing it from siblings like 'delete_elements', 'update_elements', or 'parameter_elements'. It explicitly mentions batch operation support, which adds specificity beyond just moving elements.

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 batch operations and unit conversion, it doesn't specify prerequisites (e.g., needing valid element IDs), exclusions (e.g., not for non-geometric elements), or when to choose other tools like 'update_elements' for different modifications. The only contextual note is about JSON-RPC 2.0 compliance, which is technical rather than usage-oriented.

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