Skip to main content
Glama

configure_render

Validate and save dimensions, frame rate, duration, and encoding settings as a renderable timeline so video output is configured correctly before export.

Instructions

Validate and save dimensions, frame rate, duration and encoding configuration as a renderable timeline.

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": {
      "timeline": "<timeline>",
      "output": "<output>"
    },
    "name": "configure_render"
  }
}

Input Schema

NameRequiredDescriptionDefault
outputYes
timelineYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare a non-read-only, non-destructive, non-idempotent mutation, and the description's 'validate and save' adds the useful detail that validation occurs before persistence. However, it omits what gets persisted or overwritten, where the config lives, and what happens on validation failure — gaps that matter given idempotentHint=false.

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?

A single front-loaded sentence with the action verb first and no filler. It is efficient, though the terseness is a poor fit for the size of the payload the tool consumes.

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?

An output schema exists, so return values need no explanation, but the input surface is a large nested object that is entirely undocumented in the schema. For a configuration tool of this complexity, one sentence leaves an agent unable to construct a valid timeline without reverse-engineering the JSON schema.

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 timeline object is deeply nested (fps, crf, width, height, direction, encodingPreset, plus a shots array with ten sub-fields). The description only gestures at four of those concepts and says nothing about product, output, shots, evidence, motion, transition, accent, or background.

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 pairs concrete verbs ('validate and save') with a specific resource ('dimensions, frame rate, duration and encoding configuration') and frames the result as a 'renderable timeline'. That is enough to separate it from render_video, export_video, and inspect_render, though it never names those siblings explicitly.

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?

Usage is only implied: the word 'renderable' suggests this is a setup step preceding render_video or export_video, but there is no explicit when-to-use, no prerequisite statement, and no exclusion against inspect_render. An agent must infer placement in the workflow.

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