Skip to main content
Glama

fusion_render_settings

Read Fusion composition attributes such as frame range, FPS, and size, and optionally set the comp render range in frames for accurate Resolve rendering.

Instructions

Read comp attributes (range, fps, size) and optionally set the comp render range (frames).

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

Input Schema

NameRequiredDescriptionDefault
endNo
clipNocurrent
compNo
startNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations exist, so the description carries the whole burden. It does not say that omitting start/end leaves the comp untouched, whether setting the range affects queued renders, what permissions or connection state are required, or what the response contains for the read path.

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?

One tight sentence with the read behaviour front-loaded and the optional write second. Nothing is wasted, though the compression contributes to the ambiguity around the read/write switch.

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 four-parameter, zero-coverage, zero-annotation tool with no output schema and two behavioural modes, the definition is too thin. An agent cannot tell which parameters trigger mutation or what the read path returns.

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 coverage is 0%, so all four parameters depend on the description. It maps 'start'/'end' loosely to the render range in frames, but never explains 'comp' or 'clip' (default 'current'), nor what units or resolution rules apply to the numeric bounds.

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?

Names a specific verb pair and resource: read comp attributes (range, fps, size) and optionally write the render range in frames. That is a recognisable dual-mode settings operation, though it does not distinguish itself from close siblings such as fusion_comp_info or render_options.

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?

The word 'optionally' implies the write only happens when a range is supplied, but the description never states that condition explicitly, never says when to prefer fusion_comp_info or render_options, and never mentions prerequisites like needing an active comp.

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