Skip to main content
Glama

status

Retrieves DaVinci Resolve version, edition, active project, timeline, playhead, page, and media pool size; call it first each session to establish current editing context.

Instructions

Overview: Resolve version/edition, current page, project, timeline, playhead and media pool size. Call first in every session.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.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 must carry the behavioral burden; 'Overview: Resolve...' implies a non-mutating read, but read-only/no-side-effect status is never stated outright. It also says nothing about response shape, cost, or whether the snapshot can go stale, which matters since there is no output schema.

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, zero filler, with the scope summary front-loaded before the usage directive. Nothing could be cut without losing information.

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 annotations, and no output schema, the enumeration of resolved values does most of the work of describing the return payload. An explicit statement that the call is side-effect free and safe to invoke at any time would close the last gap.

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 no parameter semantics to explain and the baseline of 4 applies. The description correctly spends no words on inputs.

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?

The description names a concrete set of resolved values (version/edition, current page, project, timeline, playhead, media pool size), which is far more specific than the bare name 'status'. It reads clearly as a read-style overview distinct from sibling setters like 'page' and 'playhead', though it never explicitly contrasts itself with them.

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 first in every session' gives an unambiguous, actionable usage rule and effectively excludes most misuse. It does not name alternatives or state when not to call it, but for a zero-parameter bootstrap call that is a minor gap.

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