Skip to main content
Glama

Outil.io

Transcribe video project

transcribe_video_project
Read-only

Transcrire le mix audible monté (hors musique legacy) via le fournisseur configuré. Renvoie une proposition de document avec sous-titres, sans sauvegarder ni écraser ceux du montage.

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": "transcribe_video_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds real value on top: it clarifies that the operation returns a proposal document with subtitles and neither saves nor overwrites the montage's existing captions. It also implies the use of an externally configured provider. It does not mention latency or cost of the external provider call, which keeps it from a 5.

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 tight sentences, correctly front-loaded: the purpose comes first, then the return and the non-destructive guarantee. There is no filler or restatement of the title.

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 two-parameter tool with no output schema, the description covers what comes back (a proposed document with subtitles) and whether anything is mutated, which is adequate. It falls short by not explaining 'version' or the prerequisite of a configured provider's format, and by not indicating the expected latency or whether the call is synchronous.

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%, so the description needs to carry the burden of explaining the parameters, but it does neither: projectId is obvious, yet 'version' (an integer greater than zero, probably a concurrency or revision guard) is left entirely unexplained. The description therefore adds no meaning beyond the raw schema, and the unexplained 'version' is a real risk of misuse.

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 verb and resource: transcribe the edited audible mix, excluding legacy music, using the configured provider. It clearly distinguishes the operation from a plain caption read or import, though it never names a sibling alternative. The French wording is understandable but slightly out of step with the English title and schema.

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?

Usage is implied by the phrase 'mix audible monté' (the edited mix) and 'via le fournisseur configuré', which signals that the provider must be set up beforehand. There is no explicit when-to-use versus when-not-to-use, and no alternative such as a caption import or a plain caption fetch is named.

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.