Loading ToolBench
This server has significant definition quality gaps. All 28 tools have names starting with action verbs (good), but descriptions are extremely brief (5-15 chars), far below the 50-200 char baseline for LLM-optimized tools. Most parameter descriptions are minimal or missing context. Input schemas are present but lack depth, no enums for constrained values, no min/max for numeric params, no format specifications. Output schemas are entirely undocumented. Error handling is absent from tool definitions. The server exposes AppleScript/JXA execution details rather than abstracting them. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels. Tools like delete_selected and import_fcpxml are destructive but lack confirmation patterns or recovery guidance.
Close the current project in Final Cut Pro
Copy selected clips in Final Cut Pro
Cut selected clips in Final Cut Pro
Delete selected clips in Final Cut Pro
Deselect all clips in the timeline in Final Cut Pro
Fit timeline to window in Final Cut Pro
Generate FCPXML footer to close an event
Generate FCPXML header for a new event
Descriptions are critically short (5-15 chars). Baseline is 50-200 chars for LLM-optimized tools. Examples: 'Play the current sequence in Final Cut Pro' (41 chars) lacks WHEN to use, prerequisites, or return value guidance. LLMs cannot reliably select tools with such minimal context.
No output schemas documented. Tools return unstructured results (e.g., getLibraries returns JSON with name, id, file, event_count), but the MCP tool definition does not declare the response structure. LLMs cannot plan downstream calls or extract fields reliably without documented output schemas.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 40 | 2026-07-28+ | v2 |
Get list of projects in a Final Cut Pro event
Get list of all Final Cut Pro libraries
Get list of events in a Final Cut Pro library
Go to the end of the sequence in Final Cut Pro
Go to the start of the sequence in Final Cut Pro
Import FCPXML content into Final Cut Pro
Open a project in Final Cut Pro
Paste clips from clipboard in Final Cut Pro
Paste and connect clips from clipboard in Final Cut Pro
Paste and insert clips from clipboard in Final Cut Pro
Pause playback in Final Cut Pro
Play the current sequence in Final Cut Pro
Redo the last undone action in Final Cut Pro
Save the current project in Final Cut Pro
Select all clips in the timeline in Final Cut Pro
Stop playback in Final Cut Pro
Toggle fullscreen mode in Final Cut Pro
Undo the last action in Final Cut Pro
Zoom in on the timeline in Final Cut Pro
Zoom out on the timeline in Final Cut Pro
Destructive tools (delete_selected, import_fcpxml) lack confirmation patterns or dry-run support. No error handling guidance in definitions. Agents can trigger irreversible actions without safeguards. Missing tool annotations (destructiveHint) that would signal risk to the LLM.
Parameter descriptions are minimal or absent. Example: open_project has library_name, event_name, project_name with 1-line descriptions. No guidance on format, constraints, or what happens if a name doesn't exist. LLMs cannot validate inputs or recover from errors.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels declared in the spec. Tools marked DESTRUCTIVE (delete_selected) or WRITE (play, pause) should carry annotations to guide agent behavior and prevent unsafe retries.