Skip to main content
Glama
Sign In
viraldar

viraldar

by ThomasRayvol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Diaporama vidéo

montage_diaporama

Creates a 1080×1920 video from ordered images with per-image durations, optional fades, transitions, and background audio, turning carousel PNGs into a ready-to-share vertical slideshow.

Instructions

Fait une vidéo 1080×1920 à partir d'images (par exemple les PNG d'un carrousel), avec une durée par image (ou une pour chacune), des fondus en option et une piste audio en option.

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": {
      "images": "<images>"
    },
    "name": "montage_diaporama"
  }
}

Input Schema

NameRequiredDescriptionDefault
fpsNoi/s (30 par défaut).
nomNoNom de sortie (sans extension), rangé dans montages/.
modeNobandes par défaut
fonduNos (0)
dureesNoUne par image
imagesYesChemins des images, dans l'ordre.
musiqueNoMusique mixée sur tout le montage (coupée à sa durée).
qualiteNonormale par défaut.
transitionNoxfade (fade)
couleurBandesNoCouleur du fond en mode bandes (#RRGGBB), noir par défaut.
dureeParImageNos (3)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden; it does disclose the fixed 1080×1920 output, that music is truncated to the montage length, and that fades and audio are optional. It omits what the agent most needs to know about a render operation: where the file lands, what the call returns, and whether it is slow or blocking.

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 that defines the output first and then the knobs, with no filler. It stays dense but readable despite packing four distinct concepts into one clause chain.

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?

For an 11-parameter render tool with a nested audio object, no annotations and no output schema, the description covers intent but not consequences — no return value, no destination path, no note about processing cost or failure modes. Adequate to attempt a call, thin for calling it correctly the first time.

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 baseline is 3, and every parameter including the nested music object is already documented in the schema. The description adds one genuinely useful clarification — that duration is either a single value for all images or one per image — but nothing about mode, quality or transition beyond what the schema says.

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 artifact: builds a 1080×1920 video from images, with per-image durations, optional fades and optional audio. That is far more concrete than the title 'Diaporama vidéo', but it never names or contrasts a sibling such as montage_assembler, so an agent cannot tell from the text alone which montage tool to pick.

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 example 'les PNG d'un carrousel' implies the typical use case (turning carousel stills into a vertical video), which is real context. There is no explicit when-to-use/when-not and no routing to or from alternatives, so the guidance is inferred rather than stated.

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