Skip to main content
Glama

get_status

Read-only

Retrieve current DaVinci Resolve status—product/version, active page, database, open project, timeline, playhead, keyframe mode, and render state—to confirm the environment before scripting.

Instructions

Resolve product/version, Studio flag, current page, database, project folder, open project, current timeline and playhead, keyframe mode and whether a render is running.

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": "get_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

Does 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. The description's added value is the enumeration of returned fields, which matters because there is no output schema, but it says nothing about behavior in edge states (no project open, render not running) or about the shape/format of the response.

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?

A single front-loaded sentence with a verb first and a dense comma-separated list of fields; every item carries information and there is no filler. Length is proportionate to a zero-argument status tool.

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?

With no parameters, no output schema, and read-only annotations, the main missing piece would be return-value coverage, and the description supplies it by naming each field. What is still absent is how the values are formatted and what happens when no project or render is active.

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 the baseline is 4; there is no parameter semantics for the description to explain. Nothing in the description misrepresents the (empty) argument set.

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?

"Resolve" plus an explicit enumeration of the state fields returned (product/version, Studio flag, page, database, project folder, open project, timeline, playhead, keyframe mode, render running) makes it clear this is a single-call status snapshot. It stops short of 5 because it describes the returned payload rather than the job to be done, and it never distinguishes itself from siblings like playhead or render_status that appear to overlap.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no named alternative. An agent cannot tell from the text whether to call this or the sibling playhead / render_status tools for a subset of the same information.

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

Deploy Server

Other Tools