Генерация и управление BIM-элементами в Revit через естественный язык. Generation and management of BIM elements in Revit through natural language.
The server defines 12 tools with complete input schemas and descriptions in Russian. Most tools follow verb_noun naming convention and have action-oriented names (generate_warehouse, create_level, delete_element, etc.). However, several critical quality gaps reduce the score: (1) Descriptions lack English translations, limiting LLM discoverability in English-speaking contexts; (2) Output schemas are not formally documented, responses are prose strings rather than structured JSON; (3) Parameter descriptions, while present, contain examples (e.g., 'например, 42.0') that LLMs may reuse literally; (4) No error handling guidance, tools return error strings but don't guide recovery steps; (5) No tool annotations (readOnlyHint, destructiveHint) despite clear risk distinctions (DELETE_ELEMENT is destructive, GET_MODEL_INFO is read-only); (6) Multi-step operations like generate_warehouse lack idempotency hints or confirmation patterns despite being write-heavy. The server targets Revit via HTTP (good transport), but tool composition shows weak chaining support, responses lack consistent ID fields to feed downstream tools. Average baseline: 194 chars for tool description (actual range 45 - 180 chars, most under ideal 100 chars).
Создаёт новый уровень (этаж) в Revit на заданной высоте.
Вставляет дверь или окно в стену-хост.
Создаёт здание произвольной полигональной формы в Revit.
Создаёт стену между двумя узлами виртуальной сетки осей.
Удаляет элемент из Revit по его client_id. client_id выдаётся при создании элемента (стена, пол, уровень).
Генерирует складское здание в Revit с заданными параметрами.
Возвращает список узлов текущей виртуальной сетки осей с их координатами в миллиметрах.
Output schemas not formally documented. Tools return free-text prose (e.g., 'Склад "name" создан в Revit!\n\n...') instead of structured JSON. LLMs cannot reliably parse responses to extract IDs and metadata for downstream tool chaining. Per pattern:response-shaper, structured output is required for agent reasoning.
Missing tool annotations. Tools with clear risk profiles (generate_warehouse=WRITE, delete_element=DESTRUCTIVE, get_model_info=READ_ONLY) lack destructiveHint/readOnlyHint annotations. Per current spec (2026-07-28), tool annotations enable agents to reason about safety and reversibility.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | C | 60 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 47 | - | v1 |
Возвращает информацию о текущем Revit-документе: уровни (с высотами), доступные типы стен и полов.
Возвращает список именованных осей (Grid) из текущего документа Revit с их координатами.
Показывает все элементы, созданные в текущей сессии Revit. Выводит client_id, тип, имя и дату создания каждого элемента. Внимание: список сбрасывается при рестарте Revit.
Создаёт или обновляет виртуальную сетку осей в сессии Revit для облегчения создания элементов на координатах.
Проверяет соответствие параметров здания нормативным требованиям.
No error guidance or recovery hints. When tools fail (e.g., 'Ошибка Revit API: HTTP 500'), responses don't indicate whether to retry, adjust input, or escalate. Per pattern:recovery-guide, errors must include actionable next steps.
Descriptions contain example values (e.g., '42.0', '18.0', '380', '"Юг", "Север"') inline. LLMs tend to reuse these literally in future calls. Per pattern:constrained-input, enums should replace inline examples, and format hints should avoid concrete numbers.
Descriptions are in Russian only. Tool descriptions are non-empty but lack English translations. Most LLMs operate on English prompts, Russian-only descriptions reduce discoverability and may confuse English-speaking agents attempting to select tools.
Weak tool chaining support. generate_warehouse returns comma-separated wall IDs and a floor ID as unstructured text (e.g., 'client_id стен: W1, W2, W3'). downstream tools like delete_element expect a single client_id parameter. No structured field naming (e.g., 'wall_ids': [...], 'floor_id': '...').
No idempotency hints. generate_warehouse, create_level, and other WRITE operations don't declare idempotency. Agents retrying on ambiguous Revit timeouts may create duplicate buildings, levels, or walls without knowing it's unsafe to retry.
Missing confirmation/dry-run pattern for destructive operations. delete_element removes elements immediately with no undo or review step. Per pattern:confirmation-request, agents should confirm destructive actions before executing.
HTTP timeout (30s) not documented in descriptions. Tools call external Revit API via urllib. Timeout errors are possible but not mentioned in tool text, so agents can't anticipate or plan for slow backends.
Parameter constraints not fully specified. validate_building_parameters has design rules (min 6×6 m, max 60×40 m, height 3 - 15 m) but these are buried in function logic, not in parameter descriptions or JSON Schema constraints (minValue, maxValue, pattern). LLMs can't see constraints without parsing docstring text.