Skip to main content
Glama
ZedMoster

Revit MCP Server

by ZedMoster

create_sheets

Create multiple Revit sheets with numbered titles and specified title blocks, optionally adding views to each sheet for documentation.

Instructions

批量创建Revit图纸并添加指定视图,遵循JSON-RPC 2.0规范。

特性:

  • 支持批量创建带编号和名称的图纸

  • 可指定标题块类型

  • 支持在图纸上添加视图

  • 完善的参数验证和错误处理

参数: ctx (Context): FastMCP上下文对象 method (str): JSON-RPC方法名,默认为"CreateSheets" params (List[Dict]): 参数列表,每个字典包含: - number (str): 图纸编号(必填) - name (str): 图纸名称(必填) - titleBlockType (str): 标题块类型名称(必填) - viewName (str, optional): 要添加到图纸的视图名称(可选) request_id (int, optional): 请求ID,默认自动生成

返回: dict: JSON-RPC 2.0格式的响应

示例: response = create_sheets(ctx, params=[ { "number": "A101", "name": "首层平面图", "titleBlockType": "A0 公制", "viewName": "标高 1" }, { "number": "A102", "name": "二层平面图", "titleBlockType": "A0 公制" } ])

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
methodNoCreateSheets
paramsNo
request_idNo

Implementation Reference

  • create_sheets is listed in ARCHITECTURAL_TOOLS array used for tool registration
    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
    ]
  • Function that registers all tools by iterating over ARCHITECTURAL_TOOLS (which includes create_sheets), MEP_TOOLS, and GENERAL_TOOLS using server.tool() decorator
    def register_tools(server: FastMCP) -> None:
        """注册所有工具到MCP服务器"""
        # 注册建筑工具
        for tool in ARCHITECTURAL_TOOLS:
            server.tool()(tool)
    
        # 注册MEP工具
        for tool in MEP_TOOLS:
            server.tool()(tool)
    
        # 注册通用工具
        for tool in GENERAL_TOOLS:
            server.tool()(tool)
  • Prompt documentation instructing to use create_sheets() to create sheets as part of asset creation strategy
    - 使用create_sheets()创建图纸
  • Call to register_tools(mcp) which registers the create_sheets tool among others
    register_tools(mcp)
  • Test file demonstrating RPC call to "CreateSheets" method, likely the underlying Revit command invoked by the MCP tool
    "method": "CreateSheets",
Behavior3/5

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

With no annotations provided, the description carries full burden. It mentions '完善的参数验证和错误处理' (comprehensive parameter validation and error handling) which is useful behavioral context. However, it doesn't disclose important traits like whether this is a destructive operation, permission requirements, rate limits, or what happens on partial failures in batch operations.

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 reasonably structured with sections for features, parameters, returns, and example. However, it includes redundant information ('遵循JSON-RPC 2.0规范' appears twice), and the example could be more concise. Some sentences don't earn their place in helping an AI agent understand tool usage.

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?

For a batch creation tool with 3 parameters, 0% schema coverage, no annotations, and no output schema, the description does a fair job. It explains the core functionality and parameters well, but lacks important context about error behavior, side effects, and integration with the broader Revit context. The JSON-RPC framing adds some structure but doesn't fully compensate for missing behavioral details.

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 in the '参数' section, explaining each parameter's purpose, required/optional status, and structure of the params array. This adds significant value beyond the bare schema. However, it doesn't explain the ctx parameter's role or provide examples of valid titleBlockType values.

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 '批量创建Revit图纸并添加指定视图' (batch create Revit sheets and add specified views), which is a specific verb+resource combination. It distinguishes from siblings like create_walls or create_floors by focusing on sheets/views rather than other Revit elements. However, it doesn't explicitly differentiate from all possible sheet-related tools (none exist in siblings).

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 doesn't mention prerequisites, when this tool is appropriate versus other creation tools, or any exclusion criteria. The '特性' (features) section lists capabilities but not usage context.

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