Skip to main content
Glama

Outil.io

Analyze video silences

analyze_video_silences
Read-only

Proposer une timeline débarrassée des silences par analyse audio locale. Sans sauvegarde ; à faire avant transitions, superpositions, pistes audio et sous-titres.

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": {
      "projectId": "<projectId>",
      "version": "<version>"
    },
    "name": "analyze_video_silences"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description reinforces this with 'Sans sauvegarde', which tells the agent the result is an unsaved proposal. The local-audio-analysis detail adds real context, but nothing is said about the shape of the returned timeline or its cost.

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?

Two compact sentences, front-loading the outcome and following with the constraint and ordering rule. The second sentence is densely packed but nothing is redundant.

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?

There is no output schema, so the description should hint at what the proposed timeline looks like, and it does not. Combined with the total absence of parameter documentation, it is adequate but leaves key details unstated.

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 description mentions neither projectId nor version. With required parameters undocumented in both places, the description fails to compensate for the gap.

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?

States a concrete action and result: proposes a silence-stripped timeline via local audio analysis. That distinguishes it from the editing/destructive siblings, though it does not explicitly contrast with propose_video_edit or inspect_video_timeline.

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 clear ordering guidance — run it before transitions, overlays, audio tracks and subtitles — and notes it does not save. It stops short of naming an alternative tool or saying when not to run it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.