Skip to main content
Glama

open_page

Switch DaVinci Resolve to the Media, Cut, Edit, Fusion, Color, Fairlight, or Deliver page so an agent can move to the right workspace for the current task.

Instructions

Switch Resolve to a page: media, cut, edit, fusion, color, fairlight or deliver.

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": {
      "page": "<page>"
    },
    "name": "open_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, giving the safety profile. The description adds nothing beyond that and the schema enum: it doesn't say whether switching pages changes any project data, discards unsaved state, or fails if no project is open.

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 front-loaded sentence with the action first and the allowed values after. No wasted wording.

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

Completeness4/5

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

For a single-enum navigation tool with annotations covering safety and no output schema, the definition is close to sufficient. The main missing piece is whether the state change has any side effects on the open project.

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

Parameters2/5

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

There is one parameter, and the description simply repeats the enum values already present in the schema. It adds no meaning about what a page represents (e.g. color vs deliver workspace) or whether the switch preserves current selection.

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?

Uses a specific verb plus resource ('Switch Resolve to a page') and enumerates the valid destinations. It is reasonably distinguishable from sibling open_project since it targets UI pages rather than projects, though it doesn't say so explicitly.

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 when-to-use or when-not-to-use guidance, no prerequisites, and no reference to alternatives such as open_project. An agent must infer that this changes the application's visible page and is distinct from loading a project.

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