Loading ToolBench
MCP server enabling clients to submit and monitor Autodesk Design Automation workitems for Revit model manipulation, including model linking and creation operations.
The server provides 3 tools with reasonable naming conventions (verb-first: link_, create_, get_). All tools have descriptions and input schemas are visible in the code. However, there are significant gaps: (1) Output schemas are not documented, the code shows WorkItemSubmissionResult and WorkItemStatus types but their structure is not defined in the visible code, making it impossible for LLMs to know what fields to extract. (2) Parameter descriptions exist but are minimal and lack important constraints (e.g., region format, GUID validation, array size limits). (3) No evidence of error handling guidance, responses don't tell LLMs how to recover from failures. (4) Tool annotations (destructiveHint, readOnlyHint, idempotentHint) are absent, forcing LLMs to reason about side effects. (5) Parameter ordering and dependencies are undocumented (e.g., does linksToAdd require modelGuid to already exist?). The definitions are functional but would not pass a production code review.
Submits a workitem to create a single Revit model in the cloud from a template.
Gets the status of a Design Automation workitem.
Submits a workitem to add or remove Revit model links in a cloud model.
Output schemas not documented. Code references WorkItemSubmissionResult and WorkItemStatus but their field structure is not visible or described. LLMs cannot plan downstream operations or extract required data.
Tool annotations missing. No destructiveHint on write operations (link_models, create_model) or readOnlyHint on get_workitem_status. LLMs cannot determine which operations are reversible.
No error handling guidance in descriptions. If a workitem fails or a model link cannot be added, LLMs have no recovery path. Descriptions do not explain failure modes or retry eligibility.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 59 | <=2025-11-25 | v2 |
| 2026-03-09 | C | 61 | - | v1 |
Parameter constraints not specified. 'region' accepts freeform strings (description says 'e.g. US, EMEA' but no enum); GUID fields lack format validation; array parameters (linksToAdd, linksToRemove) lack size constraints or required field documentation.
Parameter descriptions are too short (10 - 30 chars). E.g., 'Region of the Autodesk cloud environment (e.g., US, EMEA)' is 57 chars but lacks detail on valid values, impact on behavior, or examples of what regions exist. Baseline is 72 chars minimum.
No confirmation or dry-run pattern for destructive operations. link_models can remove model links and create_model creates new models, both are irreversible but lack a confirm_before_execute mechanism.
linkModification objects lack full documentation. The items in linksToAdd/linksToRemove have modelName and modelGuid, but descriptions don't clarify: is modelGuid required or optional? Does modelName alone suffice? What happens if both are provided?