Skip to main content
Glama

disable_background_tasks

Destructive

Disables proxy, cache, and analysis background tasks in DaVinci Resolve for the remainder of the current session.

Instructions

Disable Resolve background tasks (proxy, cache, analysis) for the rest of this Resolve session.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation profile is known. The description adds genuine context beyond that: the effect is scoped to the current Resolve session and covers three named subsystems. It does not say whether the change is reversible, whether a re-enable step exists, or what happens to in-flight tasks.

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 sentence with zero filler, front-loaded with the action and immediately followed by the scope qualifier. Nothing could be removed without losing information.

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 zero-parameter session toggle, the description covers what is affected and how long the effect lasts, which is what an agent needs to decide to call it. The main residual gap is the absence of any note on re-enabling or reversibility, which matters given the destructive annotation.

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?

The tool takes zero parameters, so the schema carries no semantics that the description must compensate for; the baseline for a parameterless tool is 4. Nothing in the description is needed to interpret arguments.

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 states a specific verb and resource ('Disable Resolve background tasks') and enumerates the affected subsystems (proxy, cache, analysis). It does not name or distinguish itself from a counterpart that would re-enable tasks, so it falls short of the top score, but the action is unambiguous.

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 phrase 'for the rest of this Resolve session' implies the context in which this applies and signals that the effect is session-limited rather than permanent. There is no explicit when-to-use vs. when-not guidance and no named alternative, so usage is only implied.

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