Skip to main content
Glama

project_settings

Read or update DaVinci Resolve project settings by applying key-value changes or retrieving specific keys and search matches.

Instructions

Read or change project settings (Project Settings dialog). With set, applies {key: value} (e.g. {"timelineResolutionWidth":"1080","timelineResolutionHeight":"1920","colorScienceMode":"davinciYRGBColorManagedv2"}). Read: keys returns those keys, search filters keys by substring; neither returns everything.

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

Input Schema

NameRequiredDescriptionDefault
setNo
keysNo
searchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden: it does disclose that this tool mutates state via `set` and that reads are incomplete, which are the two most important behavioral facts. It omits whether changes persist or can be undone, what a successful `set` returns, and how invalid keys are handled - significant gaps for an unannotated mutation tool.

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?

Dense and front-loaded: mutation semantics come first, read modes second, the partiality caveat last. The inline JSON example earns its space by showing the exact key/value shape, though the trailing clause 'neither returns everything' is slightly compressed and could be clearer about what is actually returned.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter, read/write tool with no annotations and no output schema, the description covers parameter meaning and one important behavioral caveat. It is not complete enough on return shape, persistence of `set`, or failure modes, which an agent needs before committing a settings change.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate, and it does give real meaning to all three parameters: `set` applies a {key: value} map with a concrete example, `keys` requests specific keys, `search` filters by substring. It leaves ambiguity about whether `set` and `keys` can be combined in one call and whether `search` returns keys alone or keys with values.

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 verb pair and resource: 'Read or change project settings', anchored to the Project Settings dialog. It clearly separates the write path (`set`) from the read paths (`keys`, `search`), so an agent can tell which mode it needs; it stops short of naming a sibling it is not, which is why this is a 4 rather than a 5.

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?

The description explains what each of the three parameters does and warns that reads are partial ('neither returns everything'), which is genuine usage guidance. It gives no guidance on prerequisites (does a project need to be open?), no advice on how to enumerate keys when neither read returns everything, and no indication of which sibling tool to use for related settings such as timeline_settings.

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