Skip to main content
Glama

close_project

Destructive

Closes the current project in DaVinci Resolve, saving it by default. Use to safely end a project session without losing changes.

Instructions

Close the current project (saving it first by default).

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

Input Schema

NameRequiredDescriptionDefault
saveNo

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 destructiveHint=true and readOnlyHint=false, and the description adds genuinely useful context that a save occurs first by default, which softens the destructiveness. It does not, however, explain what happens when save is set to false — whether unsaved changes are discarded silently or an error is raised — which is the key behavioral question for a destructive close.

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?

A single short sentence with the action front-loaded and the default behavior in a parenthetical. Nothing is wasted and nothing is buried.

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 one-parameter tool this covers the essential action and default, but with destructiveHint=true and no output schema, the description should state the risk of dropping unsaved work when save is false. That omission is the one gap an agent would plausibly need to make a safe call.

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 description coverage is 0%, so the description carries the burden, and it does explain the single parameter: save defaults to true and causes a save before closing. It stops short of spelling out the save=false consequence, but the parameter's meaning and default are made explicit.

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 ("Close the current project") with a clear scope implied by "current," so an agent can distinguish it from save_project or delete_project. It does not explicitly name any sibling or contrast itself with them, 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?

The parenthetical "saving it first by default" implies this is the normal end-of-session action, and usage is inferable from the semantics of "close." However, there is no explicit guidance on when to choose this over save_project, archive_project, or delete_project, and no stated prerequisite that a project be open.

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