Skip to main content
Glama
Sign In
viraldar

viraldar

by ThomasRayvol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Assembler des plans

montage_assembler

Assemble ordered video clips or images into a 9:16 montage with crossfades, consistent formatting, and optional music, producing one output video for TikTok-style edits.

Instructions

Met bout à bout plusieurs plans (vidéos, chacune avec son passage, ou images avec leur durée), tous mis au 9:16 de la même façon, avec des fondus entre eux et une musique en option. Pour du texte par-dessus, enchaîner avec montage_texte.

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": {
      "plans": "<plans>"
    },
    "name": "montage_assembler"
  }
}

Input Schema

NameRequiredDescriptionDefault
fpsNoi/s (30 par défaut).
nomNoNom de sortie (sans extension), rangé dans montages/.
modeNo9:16 : recadrer (coupe les bords), flou (fond flouté), bandes (fond uni), auto (recadrer si presque vertical, sinon flou).
fonduNos (0 = coupe franche)
plansYesLes plans, dans l'ordre.
musiqueNoMusique mixée sur tout le montage (coupée à sa durée).
qualiteNonormale par défaut.
transitionNoxfade : fade, fadeblack, dissolve, slideleft, wipeleft, circleopen, zoomin…

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It explains the composition operation but omits important behavioral traits: it is a write/export operation that creates a file, yet does not state whether existing output is overwritten, how long processing may take, what permissions are required, or what the tool returns.

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?

Two sentences, front-loaded with the core operation and ending with the routing hint. There is no redundant wording or padding.

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 complex (8 parameters, nested objects, no output schema, no annotations), and the description covers the essential purpose and one important sibling hand-off. However, it leaves gaps around side effects, output format, and runtime behavior that an agent would need for confident invocation.

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 100%, so the schema already documents every parameter including defaults and enums. The description adds some useful framing—videos use a 'passage' (debut/fin) while images use a duration, all shots are normalized the same way, and music is optional—but this goes only slightly beyond the schema and does not explain the nested per-shot or music fields in more depth.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ('met bout à bout' = concatenates) and resource ('plans'), plus key facets: video clips with in/out points, images with duration, uniform 9:16 normalization, fades and optional music. It explicitly distinguishes the tool from the sibling montage_texte for text overlays, so an agent can select it without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the primary use case (assembling multiple clips/images into one sequence) and explicitly routes text-overlay needs to montage_texte. That is a clear alternative for a common follow-up, but it does not spell out when to prefer or avoid related siblings such as montage_diaporama or montage_format_tiktok.

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