Skip to main content
Glama

list_constants

Read-only

Retrieve live constant values by name, with optional prefix filtering, to inspect DaVinci Resolve scripting constants such as EXPORT_ or CACHE_ before using them in scripts.

Instructions

Resolve constants (name -> live value), optionally filtered by prefix, e.g. EXPORT_, CACHE_, AUTO_CAPTION_, COMPOSITE_, RETIME_, SCALE_, MARKER_, CLOUD_.

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

Input Schema

NameRequiredDescriptionDefault
prefixNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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, covering the safety profile. The description adds one genuinely new behavioral fact — values returned are 'live', i.e. dynamic rather than static enumerations — but says nothing about result shape, ordering, or pagination behavior.

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

Conciseness4/5

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

The core purpose is front-loaded in the first clause, with the filter semantics immediately after. The long tail of eight example prefixes is somewhat noisy, but each is a real-world anchor rather than filler, so it earns most of its space.

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 simple read-only, single-optional-parameter tool with no output schema, the description covers what it does, what it returns (live values), and how filtering works. The remaining gaps — default all-results behavior when prefix is empty, and result ordering — are minor.

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 coverage for the single 'prefix' parameter is 0%, so the description must carry the meaning, and it does: it explains that filtering is by prefix and supplies concrete prefix examples (EXPORT_, CACHE_, AUTO_CAPTION_, etc.) that illustrate the naming convention. It stops short of stating whether matching is case-sensitive or an exact-prefix match, keeping it out of 5 territory.

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 specific verb and resource ('Resolve constants') and clarifies the direction of resolution with '(name -> live value)', which tells an agent exactly what comes in and what comes out. The resource 'constants' is unique among the list_* siblings, so no explicit sibling comparison is needed, though none is offered.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: an agent can infer this is the tool for turning constant names into current values, and that the prefix filter is optional. There is no explicit when-to-use/when-not guidance, no mention of what happens when the filter matches nothing, and no routed alternative.

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