No user-submitted related servers found.
Scored across 9 tools
The generic fc_exec overlaps heavily with the specialized fc_import, fc_export, and fc_render_frame tools, since those operations are almost certainly also valid command IDs — an agent may be unsure which path to take. Similarly, fc_list_commands (returns parameter schemas) and fc_describe (returns parameter schema for one command) have fuzzy boundaries. Descriptions help somewhat, but the escape-hatch-plus-wrappers design creates real selection ambiguity.
All tools use a consistent fc_ prefix with snake_case verb_noun structure (fc_list_commands, fc_list_export_presets, fc_import, fc_export, fc_render_frame). Minor deviation: fc_exec is an abbreviation while other verbs are spelled out (fc_describe, fc_inspect), but the pattern is still clearly readable and predictable.
Nine tools is well within the sweet spot for a domain-control server. Each tool corresponds to a distinct capability — discovery, inspection, execution, media ingest, probing, export, and frame rendering — with no filler.
The surface covers the editing lifecycle well: discover commands, execute them, inspect project/sequence state, import media, probe files, list presets, export, and render frames. The generic fc_exec acts as an escape hatch for missing operations (project save/create, sequence edits), so no hard dead ends, though a non-expert agent must discover command IDs to fill those gaps.