Skip to main content
Glama
Positronikal

DaVinci MCP Professional

by Positronikal

open_project

Open a specific DaVinci Resolve project by entering its name, enabling direct project selection without manual browsing.

Instructions

Open a project by name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the project to open

Implementation Reference

  • The actual implementation of the open_project tool. It connects to DaVinci Resolve's project manager, checks if the project exists, loads it via LoadProject(), and updates the current project reference.
    def open_project(self, name: str) -> bool:
        """Open a project by name."""
        self._ensure_connected()
    
        if not self._project_manager:
            return False
    
        # Check if project exists
        projects = self.list_projects()
        if name not in projects:
            raise ValueError(
                f"Project '{name}' not found. Available: {', '.join(projects)}"
            )
    
        result = self._project_manager.LoadProject(name)
        if result:
            self._current_project = self._project_manager.GetCurrentProject()
            logger.info(f"Opened project: {name}")
    
        return bool(result)
  • The schema/definition of the open_project tool, defining it as an MCP Tool with name 'open_project', description, and input schema requiring a 'name' string parameter.
    types.Tool(
        name="open_project",
        description="Open a project by name",
        inputSchema={
            "type": "object",
            "properties": {
                "name": {
                    "type": "string",
                    "description": "The name of the project to open",
                }
            },
            "required": ["name"],
        },
    ),
  • The dispatch routing in the MCP server's _call_tool method that maps the 'open_project' name string to the resolve_client.open_project() call and formats the response.
    elif name == "open_project":
        name_arg = arguments.get("name", "")
        result = self.resolve_client.open_project(name_arg)
        return (
            f"Successfully opened project '{name_arg}'"
            if result
            else f"Failed to open project '{name_arg}'"
        )
  • The server handler registration that wires up the call_tool handler which ultimately dispatches to _call_tool.
    def _register_handlers(self) -> None:
        """Register MCP server handlers."""
    
        @self.server.list_tools()
        async def handle_list_tools() -> list[types.Tool]:  # type: ignore[reportUnusedFunction]
            return get_all_tools()
    
        @self.server.call_tool()
        async def handle_call_tool(  # type: ignore[reportUnusedFunction]
            name: str, arguments: dict[str, Any] | None = None
        ) -> list[types.TextContent]:
Behavior2/5

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It only states 'open', implying state mutation, but does not mention effects on current project, permissions needed, error handling, or safety. This is a significant gap for a state-changing 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?

The description is extremely concise at 4 words, but it is a fragment rather than a complete sentence. It is front-loaded and has zero waste, but the brevity sacrifices structure and clarity. A 5 would require a complete sentence with scope.

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

Completeness2/5

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

Given the simplicity of the tool (1 param, no output schema), the description should still explain the outcome (e.g., sets as current project) and any side effects. It lacks information on return values, errors, or prerequisites, making it incomplete for reliable agent use.

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 100% with a description for the 'name' parameter. The description adds no extra context beyond 'by name', so it meets the baseline. No additional semantics like case sensitivity or format are provided, but the schema already covers the parameter's purpose.

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 'Open a project by name' clearly identifies the action (open) and resource (project), distinguishing it from siblings like create_project or list_projects. However, it lacks specificity on what 'open' entails (e.g., navigates to, sets as current), which would elevate it to 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like get_current_project or list_projects. There are no prerequisites, no exclusions, and no context on expected state (e.g., project must exist). This is insufficient for effective decision-making.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Positronikal/davinci-mcp-professional'

If you have feedback or need assistance with the MCP directory API, please join our Discord server