MCP server for Autodesk Revit that provides methods to interact with Revit documents, including adding levels (标高) and other architectural operations
Single tool '新增标高' (add_level) has critical definition gaps. Tool name is in Chinese and lacks English verb prefix (should be 'create_level' or 'add_level'). Description is bilingual but adequate (~120 chars). Input schema present with 'offset' parameter (double type, 3000mm default), but parameter description is minimal and lacks validation bounds. No output schema documented, response structure unknown to LLM. No error handling guidance. Tool performs a WRITE operation (creates Revit level) but lacks idempotent/destructive annotations. Overall definition quality is below baseline for production use.
执行新增标高的核心逻辑。Creates a new level (elevation) in the Revit document with an optional offset from the highest existing level.
Tool name is Chinese ('新增标高') without English verb prefix. LLMs expect English names starting with action verbs (create_, add_, update_). Non-English names break tool discovery and intent parsing.
No output schema documented. LLM cannot predict response structure (fields, types, IDs for chaining). Response is inferred as 'ElementModelRequest' but structure is opaque.
Parameter 'offset' lacks validation bounds. Description says 'default 3000' but no min/max specified. Unbounded double allows LLM to pass absurd values (negative, 1e10) that break Revit API.
No error handling guidance. Tool throws 'InvalidOperationException' if no levels exist, but LLM receives raw exception with no recovery hint. Should return 'No levels found. Create a base level first.' with actionable next step.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 32 | 2026-07-28+ | v2 |
Destructive operation (creates permanent Revit element) lacks idempotent/destructive annotations and confirmation pattern. No dry-run or undo mechanism. Agent cannot safely retry on ambiguous failures.