Skip to main content
Glama

select_host

Choose which editor to drive: Premiere Pro, DaVinci Resolve, standalone ffmpeg rendering, or auto re-detect. Set the host before running edits so OpenEdit targets the right application.

Instructions

Choose the editor to drive: "premiere" (needs the OpenEdit panel open in Premiere Pro), "resolve" (DaVinci Resolve running with scripting enabled), "standalone" (no editor; edits are rendered with ffmpeg), or "auto" to re-detect.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "host": "<host>"
    },
    "name": "select_host"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full behavioral burden and does disclose environment prerequisites per host, which is valuable. However it doesn't say whether the selection persists across calls, what happens if the chosen editor isn't available, or what the tool returns on success or failure, leaving meaningful behavioral questions unanswered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence with the action first and the option list second; every clause adds prerequisite information and nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-enum selection tool with no output schema, this is close to complete: it names the choices and their required environments. Missing are the outcome of the call (status of the newly selected host) and failure behavior when the requested editor isn't running.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must explain the single parameter — and it does, defining each of the four enum values and the precondition attached to it ('auto' = re-detect, 'standalone' = ffmpeg rendering). The only gap is that it doesn't say whether re-detection discards a manual choice.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource ('Choose the editor to drive') and immediately enumerates the four selectable targets, so an agent knows this sets the active editing backend rather than querying it. The parentheticals make each option concrete and distinguishable from sibling actions like editor_status or render.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear selection context by stating the prerequisite for each option (Premiere panel open, Resolve scripting enabled, ffmpeg for standalone), which is effectively when-each-value-is-valid guidance. It stops short of saying when to prefer 'auto' over an explicit re-selection, or how this relates to checking state via editor_status first.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.