Skip to main content
Glama

batch

Execute multiple DaVinci Resolve tool calls in one round trip using an ordered steps array of tool names and arguments, reducing repeated requests.

Instructions

Run several tools in one round trip: steps = [{"tool": "razor", "args": {"times": [3.2]}}, …]. Images from preview tools are not returned here (call them directly).

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": {
      "steps": "<steps>"
    },
    "name": "batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
stepsYes
stop_on_errorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden, yet it discloses only one trait (preview images excluded). It says nothing about execution order, whether steps run sequentially or in parallel, what happens to remaining steps when one fails, or how per-step results/errors are represented.

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?

Two short sentences with the example inline and the main caveat front-loaded after the core definition. Nothing is redundant. The terseness borders on under-specification, but no sentence is wasted.

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?

For a meta-execution tool with no annotations, no output schema, and zero schema coverage, this is thin. An agent can construct a call but cannot predict result shape, ordering, or failure semantics, which are exactly the things that decide whether a batch is safe to 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 description coverage is 0%, so the description must compensate. It does well for `steps`, spelling out the object shape with `tool` and `args` and a worked example, which the schema (bare array of objects with additionalProperties:true) does not convey. But `stop_on_error` is never mentioned, so its default-true abort behavior is left entirely unexplained.

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: run several tools in one round trip, and shows the concrete `steps` shape with a tool/args example. It is distinguishable from siblings because it wraps them rather than performing a media operation itself. It stops short of a 5 only because it never says what the result of a batch looks like.

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?

One genuine routing rule is given: images from preview tools are not returned here, so call those directly (e.g. frame_preview, frames_contact). Beyond that there is no guidance on when batching beats sequential calls, whether steps may depend on each other's output, or how `stop_on_error` changes the decision.

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