Skip to main content
Glama

create_project_folder

Creates a project-manager folder in the current directory or under a specified parent, organizing DaVinci Resolve project files in the desired location.

Instructions

Create a project-manager folder in the current folder (or in parent).

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

Input Schema

NameRequiredDescriptionDefault
nameYes
parentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare the write-but-non-destructive, closed-world profile, so the description needn't repeat safety semantics. It does add one useful behavioral fact — that the default target is the current folder — but says nothing about name collisions, required permissions, or whether the created folder is returned.

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?

A single tight sentence with the primary action front-loaded and the optional location qualifier after it. Nothing is redundant, though there is very little content to structure.

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 simple two-parameter creation tool with annotations and no output schema, the description covers the essentials of what and where. It stops short of failure modes (duplicate names, invalid parent) that an agent would need to invoke it confidently.

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%, and the description clarifies that `parent` is optional and falls back to the current folder, which genuinely resolves the ambiguous `default: null` in the schema. The required `name` parameter receives no explanation at all, leaving half the surface undocumented.

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 pairs a specific verb ("Create") with a specific resource ("project-manager folder"), so the agent knows exactly what object is produced. It does not, however, distinguish this from siblings like create_project or create_bin, which an agent must choose between.

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?

The description states where the folder lands but gives no when-to-use guidance, no mention of alternatives such as create_bin or create_project, and no prerequisites. The parenthetical about `parent` is a location detail rather than routing 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