Skip to main content
Glama

editor_status

Shows which video editor OpenEdit is driving, whether it is connected, and the active project or sequence. Call this first to confirm the target editor before editing.

Instructions

Show which video editor OpenEdit is driving (premiere, resolve, or standalone ffmpeg), whether it is connected, and the active project/sequence. Call this first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "editor_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/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 burden, and it does disclose the informational payload (editor identity, connection status, active project/sequence), which is the key behavioral fact. However, it never explicitly states that the call is read-only with no side effects, nor does it describe failure behavior when no host is connected — meaningful gaps for a no-annotation tool.

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?

Two sentences, no waste, and the informative content (what is shown) is front-loaded before the imperative directive. Every clause contributes a distinct fact.

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 zero-parameter status tool with no output schema, the description successfully enumerates the returned fields, so an agent knows what it gets back. It is only slightly incomplete in not covering the disconnected/error case or its relationship to select_host.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The description correctly implies no input is needed.

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

Purpose4/5

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

States a concrete reporting action and enumerates exactly what is reported: the host editor (premiere, resolve, standalone ffmpeg), connection state, and active project/sequence. That is far more specific than the name alone. It stops short of explicitly contrasting with the sibling select_host, which an agent might confuse with a status check.

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?

"Call this first" gives an explicit ordering directive, which is real guidance for an agent orienting itself before other operations. There are no when-not conditions or named alternatives (e.g., how this relates to select_host), so it falls short of the top band.

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