Skip to main content
Glama
ZedMoster

Revit MCP Server

by ZedMoster

create_ducts

Create and batch generate ducts in Revit with automatic unit conversion, type matching, and error handling for HVAC system design.

Instructions

在Revit中创建风管,支持批量创建,遵循JSON-RPC 2.0规范。 mcp_tool使用时params不要有任何注释信息

特性:

  • 支持批量创建多个风管

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

  • 自动匹配风管类型和系统类型

  • 支持指定风管尺寸

  • 完善的错误处理机制

参数: ctx (Context): FastMCP上下文对象 method (str): JSON-RPC方法名,默认为"CreateDucts" params (List[Dict]): 风管参数列表,每个字典包含: - ductTypeName (str): 风管类型名称 - systemTypeName (str): 风管系统类型名称 - startX (float): 起点X坐标(毫米) - startY (float): 起点Y坐标(毫米) - startZ (float): 起点Z坐标(毫米) - endX (float): 终点X坐标(毫米) - endY (float): 终点Y坐标(毫米) - endZ (float): 终点Z坐标(毫米) - width (float): 风管宽度(毫米) - height (float): 风管高度(毫米)

返回: 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_ducts(ctx, params=[ { "ductTypeName": "默认", "systemTypeName": "送风", "startX": 0, "startY": 0, "startZ": 3000, "endX": 5000, "endY": 0, "endZ": 3000, "width": 300, "height": 200 }, { "ductTypeName": "矩形风管", "systemTypeName": "送风", "startX": 5000, "startY": 0, "startZ": 3000, "endX": 5000, "endY": 5000, "endZ": 3000, "width": 300, "height": 200 } ])

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
methodNoCreateDucts
paramsNo

Implementation Reference

  • Definition of MEP_TOOLS list including create_ducts for tool registration
    MEP_TOOLS = [
        create_ducts, create_pipes, create_cable_trays
    ]
  • Registration loop for MEP tools including create_ducts using server.tool() decorator
    # 注册MEP工具
    for tool in MEP_TOOLS:
        server.tool()(tool)
  • Import of tools including create_ducts from .tools module
    from .tools import *
  • Prompt mentioning usage of create_ducts tool
    - 使用create_ducts()创建风管
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: batch creation capability, automatic unit conversion (mm to feet), automatic matching of duct and system types, and comprehensive error handling. It also describes the JSON-RPC 2.0 protocol usage. However, it doesn't mention permissions, rate limits, or side effects beyond creation.

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 contains some redundant information. The JSON-RPC protocol mention appears twice, and the example is quite lengthy. While informative, it could be more streamlined by removing repetition and shortening the example.

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?

For a creation tool with no annotations and no output schema, the description does well by covering purpose, parameters, return format (both success and error cases), and providing an example. It explains the JSON-RPC response structure which compensates for missing output schema. However, it lacks information about prerequisites, permissions, or integration context with other tools.

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?

With 0% schema description coverage (schema only shows 'method' and 'params' as generic objects), the description fully compensates by providing detailed parameter documentation. It explains the 'params' array structure with 10 specific fields, their data types, units (millimeters), and purpose. This adds significant value beyond the minimal schema.

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中创建风管' (create ducts in Revit) with the specific verb '创建' (create) and resource '风管' (ducts). It distinguishes from siblings like create_pipes, create_walls, etc. by specifying the exact resource type. However, it doesn't explicitly differentiate from other creation tools beyond naming the resource.

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?

No guidance is provided on when to use this tool versus alternatives like create_pipes or other creation tools. The description mentions '支持批量创建' (supports batch creation) which hints at a use case, but doesn't provide explicit when/when-not scenarios or mention sibling tools as alternatives for different creation needs.

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