Skip to main content
Glama

set_high_priority

Sets DaVinci Resolve to high process priority so rendering and compute-heavy tasks receive more CPU time and finish reliably.

Instructions

Give Resolve high process priority (e.g. while rendering).

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": {
      "enabled": "<enabled>"
    },
    "name": "set_high_priority"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this is a non-readOnly, non-destructive, closed-world mutation, so the safety profile is covered. The description adds useful context that the mutation targets the process priority of the app itself, but it omits whether the setting persists across sessions and whether passing false restores normal priority — meaningful for a system-level toggle.

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 short sentence, front-loaded with the action and resource, with a compact parenthetical example. No filler or redundancy.

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?

The tool is simple (one boolean, no output schema), and the description conveys enough to call it in the common case. However, with zero schema coverage on the only parameter and no statement of the false-path behavior, a small but real informational gap remains.

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?

Schema description coverage is 0% and the single parameter `enabled` is never mentioned. The description only narrates the 'on' direction ('give high priority'), leaving the agent to guess that false disables it, which is exactly the gap the description should have closed.

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 object — giving the Resolve process high OS priority — which is distinguishable from sibling setters like set_current_bin or set_project_settings. It is clear what the tool does, though it never clarifies the inverse (lowering/parking priority) that the `enabled` flag implies.

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 '(e.g. while rendering)' implies the intended context for raising priority, so an agent can infer when it is useful. There is no explicit when-not guidance, no note about restoring normal priority afterwards, and no named alternative.

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