Local Windows computer-use plugin implementation with Codex and Claude Code adapters for controlling Windows applications via MCP
18 tools with complete input schemas and descriptions. Naming follows verb_noun convention (list_, get_, click_, etc.). Descriptions are present but brief (10-50 chars typical), below the 50-200 char LLM-optimized baseline. Window reference parameter is well-documented with extensive metadata fields. Error handling and output schemas are not visible in provided code. No evidence of pagination, result limits, or recovery guidance in descriptions. Tool composition is sound (single responsibility), but descriptions lack context on when/why to use each tool.
Activate Window
Click Coordinates
Click UIA Element
Drag Pointer
End Computer Use Turn
Refresh Window Reference
Get Window State
Launch Or Reuse App
List Windows Apps
Descriptions are uniformly brief (10-50 chars), below the 50-200 char LLM-optimized baseline. Lack context on when/why to use each tool, dependencies, and prerequisites.
No output schemas documented in provided code. LLMs cannot plan downstream calls or extract required fields without knowing response structure.
No error handling guidance visible. Error responses should tell LLM what to do next (retry, ask user, or fail). Currently no recovery patterns documented.
Discovery tools (list_apps, list_windows) lack pagination parameters (limit, offset, cursor) and result count documentation. Large result sets risk context window exhaustion.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 57 | 2025-06-18+ | v2 |
List Open Windows
Run UIA Secondary Action
Press Key
Scroll At Point
Select File In Dialog
Select Folder In Dialog
Set Save Path In Dialog
Set UIA Value
Type Text
Window reference parameter is complex with 20+ optional fields. Descriptions do not explain which fields are required for different tool calls or how to populate them.