Skip to main content
Glama
ZedMoster

Revit MCP Server

by ZedMoster

create_floor_plan_views

Create floor plan views from specified levels in Revit, supporting batch creation and automatic handling of existing views to prevent duplicates.

Instructions

根据给定标高创建楼层平面视图,遵循JSON-RPC 2.0规范。 mcp_tool使用时params不要有任何注释信息

特性:

  • 支持批量创建多个楼层平面视图

  • 自动跳过已存在的视图,避免重复创建

  • 完善的错误处理机制

参数: ctx (Context): FastMCP上下文对象 method (str): JSON-RPC方法名,默认为 CreateFloorPlanViews params (List[Dict]): 视图参数列表,每个字典包含: - levelId (str): 标高的ElementId - viewName (str): 要创建的视图名称

返回: 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 = create_floor_plan_views(ctx, params=[ {"levelId": "123456", "viewName": "Level 1 - Floor Plan"}, {"levelId": "789012", "viewName": "Level 2 - Floor Plan"} ])

# 返回示例
{
    "jsonrpc": "2.0",
    "result": [
        {
            "elementId": "123789",
            "name": "Level 1 - Floor Plan",
            "familyName": "Floor Plan"
        },
        {
            "elementId": "123790",
            "name": "Level 2 - Floor Plan",
            "familyName": "Floor Plan"
        }
    ],
    "id": 1
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
methodNoCreateFloorPlanViews
paramsNo

Implementation Reference

  • Defines the ARCHITECTURAL_TOOLS list that includes the create_floor_plan_views tool function, imported from .tools.
    ARCHITECTURAL_TOOLS = [
        create_levels, create_floor_plan_views, create_grids, create_walls, create_floors,
        create_door_windows, create_rooms, create_room_tags, create_family_instances, create_sheets
    ]
  • Registers all architectural tools, including create_floor_plan_views, to the FastMCP server using server.tool() decorator.
    for tool in ARCHITECTURAL_TOOLS:
        server.tool()(tool)
  • Usage instruction for the create_floor_plan_views tool in the asset creation strategy prompt.
    - 使用create_floor_plan_views()为每个标高创建平面视图
  • Test script demonstrating the RPC call to CreateFloorPlanViews method with example parameters, likely corresponding to the tool's implementation logic.
    # 构造 JSON-RPC 请求
    json_rpc_request = {
        "jsonrpc": "2.0",
        "method": "CreateFloorPlanViews",
        "params":
            [
                {"levelId": "355", "viewName": "Level 1 - Floor Plan"},
                {"levelId": "2607", "viewName": "Level 2 - Floor Plan"}
            ]
        ,
    }
    
    # 发送更新元素数据
    send_tcp_data(json_rpc_request)
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 effectively describes key behaviors: supports batch creation, automatically skips existing views to avoid duplicates, and has error handling. These traits go beyond basic functionality and help the agent understand how the tool operates, though it could mention permissions or 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.

Conciseness3/5

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

The description is front-loaded with the core purpose but includes extensive technical details (JSON-RPC spec, example code, return structure) that may overwhelm. While informative, some sections like the full return format could be streamlined. It's structured but not optimally concise for quick agent comprehension.

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 (batch creation tool with no annotations or output schema), the description is fairly complete. It covers purpose, parameters with semantics, behavioral traits, and return format, though it lacks output schema support. The example aids understanding, but more context on error scenarios or integration with siblings would enhance completeness.

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 details the 'params' parameter structure, specifying 'levelId' and 'viewName' with examples, which adds significant meaning beyond the generic schema. However, it doesn't explain the 'method' parameter's purpose or default value, leaving a minor gap in parameter understanding.

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: '根据给定标高创建楼层平面视图' (create floor plan views based on given elevations). It specifies the verb '创建' (create) and resource '楼层平面视图' (floor plan views), making the action explicit. However, it doesn't differentiate from sibling tools like 'create_walls' or 'create_floors' beyond the resource type, 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. It mentions JSON-RPC 2.0 compliance and technical usage notes (e.g., 'params不要有任何注释信息'), but offers no context about prerequisites, when this is appropriate compared to other creation tools, or any exclusions. This leaves the agent without practical usage direction.

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