Skip to main content
Glama
Sign In
viraldar

viraldar

by ThomasRayvol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Rendre un carrousel

carrousel_rendre

Render a TikTok carousel from JSON into one PNG or JPEG image per slide plus an editable carousel.json, returning file paths and layout warnings.

Instructions

Rend un carrousel TikTok décrit en JSON : une image par diapositive (PNG, ou JPEG pour l'envoi par l'API TikTok) dans /carrousels// (01.png, 02.png…), plus carrousel.json (l'entrée, pour retoucher). Renvoie les chemins et des avertissements (texte coupé, trop réduit, hors de la zone sûre du cas zone, image introuvable). Voir carrousel_modeles pour les champs et des exemples ; vérifier ensuite avec carrousel_apercu.

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": {
      "nom": "<nom>",
      "modele": "<modele>",
      "diapositives": "<diapositives>"
    },
    "name": "carrousel_rendre"
  }
}

Input Schema

NameRequiredDescriptionDefault
nomYesNom du carrousel : le dossier de sortie (carrousels/<nom>/)
zoneNoZone sûre : description, sans_description, pub (défaut « description » ; détail dans carrousel_modeles ou montage_infos).
themeNoCouleurs (CSS) et polices ; chaque modèle a les siennes par défaut
formatNo9:16 plein écran ; 3:4 presque entier sous une description ; 4:5 toujours entier9:16
langueNofr
modeleYes
sortieNojpeg pour l'API TikTokpng
varianteNonotes : « app » (par défaut) ou « papier » ; natif : « bandeau » (par défaut), « contour » ou « bandeau_noir »
signatureNo@compte affiché discrètement en haut de chaque diapositive
diapositivesYes
numerotationNoAffiche 2/7 en haut à droite

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the write location, the extra carrousel.json copy kept for retouching, and the warning categories returned (text truncated, over-reduced, outside the safe zone for the `zone` case, missing image). It does not say whether an existing folder is overwritten or how expensive a render is.

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?

Three sentences, front-loaded with the output layout before the return/warning behavior and the sibling pointers. Dense but every clause carries information; the parenthetical warning list is the only slightly bulky part.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter tool with nested slide objects and no output schema, the description covers where files land, what is returned, what warnings mean, and which sibling to read next. Remaining gaps (overwrite behavior, render cost, error/failure modes) are modest rather than blocking.

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 coverage is 73% with four enums and nested slide objects, so the schema already does most of the work. The description reinforces a few meanings (jpeg for the TikTok API, safe-zone warnings tied to `zone`, image-not-found tied to image paths) but adds no format or constraint detail beyond what the schema states.

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?

States a specific verb and resource ('Rend un carrousel TikTok décrit en JSON') and immediately pins down the output artifacts: one image per slide, naming convention 01.png/02.png, plus carrousel.json in carrousels/<nom>/. It also distinguishes itself from siblings by routing to carrousel_modeles for field docs and carrousel_apercu for verification.

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?

Gives a clear workflow: consult carrousel_modeles for fields and examples first, render, then verify with carrousel_apercu. It lacks any explicit exclusion (e.g. when to prefer the montage_* siblings for single-image work), so the when-not side is left to inference.

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