Skip to main content
Glama

page

Retrieves the active DaVinci Resolve workspace or switches to a specified workspace such as Media, Cut, Edit, Fusion, Color, Fairlight, Deliver, or Photo.

Instructions

Get the current page, or switch to one of: media, cut, edit, fusion, color, fairlight, deliver, photo.

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

Input Schema

NameRequiredDescriptionDefault
nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose the read/write duality ('switch to') that an agent must know before calling. However it is silent on failure behavior for unrecognized page names, whether the switch is persistent or a UI-only change, and whether the response reflects the new or old page.

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 96-character sentence, front-loaded with the primary read action and the write action immediately after. Every clause carries information; nothing is padding.

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 one-optional-parameter tool with no annotations and no output schema, the description covers the value domain and the mode switch, which is the core need. It could say a bit more about the returned value and error handling, but the gaps are minor at this complexity level.

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% and the parameter has no enum, so the description is the only source of valid values — and it lists all eight page names plus the default no-argument read behavior. It adds real meaning beyond the bare `name: string|null` schema, losing a point only for not specifying case sensitivity or matching rules.

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 names a specific verb pair ('get'/'switch') and the resource ('page'), then enumerates every valid target value, so an agent knows exactly what the tool reads and writes. It lacks only the domain framing (what a 'page' is in this workspace), 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 Guidelines4/5

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

The sentence implicitly defines two modes: call with no argument to read the current page, call with a name to switch. The alternatives are enumerated rather than merely alluded to. It stops short of stating what happens on an invalid name or why one would switch, so exclusions are absent.

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