revit-tunnel-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_tunnel_segment_catalogA | 列出可用管片布局、角色、角度以及族内容配置和版本；不会修改 Revit。 |
| preview_tunnel_segmentsA | 校验布局、族版本、线形与尺寸，返回每块独立管片的完整计划和预览令牌；不会修改 Revit。 |
| inspect_tunnel_segment_batchA | 按批次标识反查每块独立管片的身份、族版本、位置、定向、包围盒和体积；不会修改 Revit。 |
| create_tunnel_segmentsA | 使用预览令牌在当前 Revit 项目中为每块管片创建独立族构件；不删除或覆盖已有元素。 |
| preview_tunnel_ringsA | 校验整体环参数并返回每环位置和预览令牌；此工具不会修改 Revit。 |
| get_tunnel_backend_statusA | 检查 pyRevit 隧道接口、Revit 版本和当前活动项目。 |
| inspect_tunnel_batchB | 按批次标识反查整体环、族、标记、包围盒、体积和定向基准；不会修改 Revit。 |
| create_tunnel_ringsA | 使用预览令牌在当前 Revit 项目中创建整体族管片环；不删除或覆盖已有元素。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct resource (catalog, backend status, segments, rings) and action (list, get, preview, inspect, create). Preview vs. inspect are clearly differentiated: preview validates and returns tokens, while inspect returns detailed properties by batch ID.
All tool names follow a consistent verb-noun snake_case pattern, using verbs like list, get, preview, inspect, and create paired with clear nouns (tunnel_segment_catalog, tunnel_segments, tunnel_rings). Minor variations like segment_batch vs batch still follow the same style.
8 tools is well within the ideal range and each tool earns its place, covering catalog, status, preview, inspect, and create for two related domain objects (segments and rings). No redundant or missing tools at the surface level.
The server covers the full preview->create->inspect lifecycle for both tunnel segments and rings, plus backend status and catalog listing. Missing update/delete operations are not critical for a creation-focused server, but could be a minor gap if modifications are needed.