Skip to main content
Glama
Sign In
viraldar

viraldar

by ThomasRayvol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Découper

montage_decouper

Extract a precise passage from a video using exact start and end times, re-encoded to the hundredth of a second without changing the resolution. Keeps the original frame size for cut-only edits.

Instructions

Garde un passage d'une vidéo (au centième de seconde près : ré-encodé), sans changer sa taille. Pour découper et mettre au 9:16 d'un coup, utiliser montage_format_tiktok avec debut/fin.

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": {
      "fichier": "<fichier>",
      "debut": "<debut>"
    },
    "name": "montage_decouper"
  }
}

Input Schema

NameRequiredDescriptionDefault
finNoFin, en s (sinon duree, sinon jusqu'au bout).
nomNoNom de sortie (sans extension), rangé dans montages/.
debutYesDébut, en s.
dureeNoDurée en s, si pas de fin.
fichierYesVidéo source.
qualiteNonormale par défaut.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden; it does disclose the two behaviors that matter most (re-encoding at centisecond precision, and that the frame size is left unchanged), which is real value. However, it says nothing about quality loss from re-encoding, source-file requirements, failure behavior, or what the call returns, which are significant gaps for an unannotated media-mutation tool.

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, zero waste, and the core behavior is front-loaded before the alternative-tool routing advice. Each sentence earns its place.

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 a 6-parameter tool with no annotations and no output schema, the description covers purpose, key behavior, and one alternative, but leaves the result unspecified — the agent cannot tell whether it receives a path, a job status, or nothing. The output naming convention is only conveyed indirectly via the nom parameter's schema text.

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 every parameter including fin/duree fallbacks and the qualite enum is already documented in the schema. The description reinforces the centisecond precision of debut/fin and echoes the debut/fin usage of the sibling, but adds no new constraints or units 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: keeps a passage of a video without changing its size, with centisecond precision and re-encoding. This is enough to distinguish it from montage_format_tiktok, which is explicitly named as the resize-to-9:16 alternative.

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 an explicit alternative and the condition that selects it ('pour découper ET mettre au 9:16 d'un coup, utiliser montage_format_tiktok'), which is exactly the kind of routing guidance that prevents a wrong tool choice. It does not state exclusions in the other direction (e.g., when this tool is preferable despite the format difference), so it falls short of full when/when-not coverage.

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