Capture the Final Cut Pro viewer, timeline, or dialogs as a screenshot to inspect edit state or resolve dialogs. Optionally limit capture to the front window instead of the full display.
Take a screenshot of Final Cut Pro so you can see the viewer, timeline or a dialog.
| Name | Required | Description | Default |
|---|---|---|---|
| window_only | No | Capture just FCP's front window (else the main display). |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description needn't repeat it. It adds that the capture targets FCP's visual surface, but says nothing about the return form (inline image vs. file path), size/resolution, or failure behavior when FCP isn't running.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One tight sentence with the purpose front-loaded and zero filler. Slightly clipped given that a screenshot tool's output form is the key operational detail an agent needs.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema exists, so the description is the only place to state what comes back — it implies a viewable image but never confirms format or whether it is returned inline. For a minimal one-parameter read tool that is adequate, but not complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and the single parameter window_only already documents 'capture just FCP's front window (else the main display)'. The description mentions neither window_only nor its default, so it adds nothing beyond the schema — baseline 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a concrete verb and resource (screenshot of Final Cut Pro) plus what it visually captures — viewer, timeline, dialog. Clear without opening the schema, but it never distinguishes itself from the sibling fcp_ui_snapshot, which plausibly overlaps.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is only implied through the 'so you can see…' rationale; there is no explicit when-to-use statement, no mention of when to prefer fcp_ui_snapshot or fcp_menu_list, and no stated prerequisites (e.g. FCP must be running/frontmost).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.