Skip to main content
Glama

get_project_settings

Read-only

Retrieve all DaVinci Resolve project settings or select specific keys such as timeline frame rate, resolution, and color science to inspect or verify project configuration.

Instructions

Project settings (all of them, or only keys, e.g. timelineFrameRate, timelineResolutionWidth, colorScienceMode...). See get_api_type('ProjectSettings') for every key and value.

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_project_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
keysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this a read-only, closed-world operation, so the safety profile is covered. The description adds real scope information — that the call returns the full settings set unless `keys` narrows it — plus a cross-reference for enumerating every key. It does not say what the returned values look like (flat map vs nested), which is the main remaining gap for a tool with 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.

Conciseness4/5

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

Two compact sentences with the primary behavior front-loaded and the filter semantics in a parenthetical. The trailing ellipsis after the example keys is slightly loose but does not obscure meaning.

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 single optional-parameter read tool with annotations covering safety, the description supplies what matters: scope, the filter's purpose, and where to find valid key names. Only the shape of the returned settings map is left unstated, which is a minor omission given no output schema exists.

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 is 0% and the schema only says 'array of strings', so the description carries the burden and does it well: it establishes that `keys` is an optional filter, shows concrete example values (timelineFrameRate, timelineResolutionWidth, colorScienceMode), and routes the agent to get_api_type('ProjectSettings') for the complete key list.

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 the resource ('Project settings') and states the two modes of operation: return everything, or return only the named `keys`. The verb is only implied by the tool name, and it never explicitly contrasts itself with the nearby get_timeline_settings, so it is clear but not fully differentiated.

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: nothing says to prefer this over get_timeline_settings or that set_project_settings is the counterpart for writes. The pointer to get_api_type('ProjectSettings') is a lookup hint for key names rather than usage guidance.

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