Skip to main content
Glama
Sign In

Outil.io

by io.outil
OverviewDiscussionsAdmin

Add voiceover

add_voiceover

Ajouter une voix off : les notes de l’orateur de chaque diapositive (écrites par l’assistant quand elles manquent) sont dites et jouées pendant la présentation. Tâche de fond : renvoie jobId (presentation_job).

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": {
      "id": "<id>"
    },
    "name": "add_voiceover"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesIdentifiant de la présentation (renvoyé par create_presentation ou list_presentations).
voiceNoVoix : F1…F5 (Claire, Élise, Anne, Léa, Hélène), M1…M5 (Louis, Victor, Hugo, Paul, Marc) ; défaut Claire.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare it is a non-read-only, non-destructive, closed-world operation. The description adds genuinely new behaviour: it is a background task that returns a jobId consumed by presentation_job, and it silently generates speaker notes where they are missing. It does not say whether existing audio is replaced or how the job is polled.

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 sentences, effect first and the background-job/return-value note second — well front-loaded with no filler. The parenthetical about assistant-written notes makes the first sentence dense but it earns its place.

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 a two-parameter task with no output schema, the description covers what the tool does, its side effect on speaker notes, and that a jobId is returned for follow-up. Missing only failure modes and whether previously generated voiceover is overwritten.

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 100% and the schema already documents the 'id' source and enumerates all voice options (F1–F5, M1–M5) with the default Claire. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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 names a specific verb and resource ('Ajouter une voix off') and explains the actual effect: each slide's speaker notes are spoken and played during the presentation. That is far more informative than the title alone, though it never contrasts itself with siblings such as rewrite_slide or generate_presentation.

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 rather than stated: the agent can infer voiceover depends on speaker notes and that missing ones are auto-written. There is no explicit 'use this when…', no prerequisite (e.g. presentation must exist and have slides), and no alternative named.

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

All Outil.io toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources