Skip to main content
Glama

open_project

Loads a DaVinci Resolve project by name, optionally from a project-manager folder path, so agents can switch to the correct project before editing or rendering.

Instructions

Open (load) a project by name, optionally from a project-manager folder path.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "open_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
folderNo

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=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only that the operation 'loads' a project and that the folder refers to a project-manager path; it does not say what happens to an already-open project, whether the call fails when the project is missing, or what state changes.

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?

One sentence, front-loaded with the action, with the optional parameter noted immediately after. No filler, no redundancy with the schema.

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 two-parameter tool with no output schema, the definition is mostly sufficient, but it omits behavior an agent would want before calling: effect on the currently open project and failure modes when the name or folder does not match. Nothing about return values is expected here since no output schema exists.

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 description coverage is 0%, so the description carries the burden. It clarifies that 'name' identifies the project and that the optional 'folder' is a project-manager folder path, which is genuinely useful given the bare schema. It stops short of format examples (path separators, case sensitivity, match behavior), leaving some ambiguity.

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 gives a specific verb and resource — 'Open (load) a project' — which is clearly distinguishable from create_project, close_project, or delete_project. It does not explicitly name or contrast with any sibling, which keeps it short of 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?

Usage is implied by 'open (load) a project': the agent can infer this is for bringing an existing project into the session rather than creating one. There is no explicit when-to-use/when-not statement, no mention of prerequisites, and no routing to alternatives such as import_project or open_page.

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