Skip to main content
Glama
Sign In

Le Scribe Audio — Transcription Audio & Vidéo (FR)

by io.github.zoulouzaza76
OverviewDiscussionsAdmin

rename_speaker_label

Idempotent

Renomme globalement l'étiquette d'un intervenant (diarisation) sur toutes ses prises de parole (ex: remplacer 'Intervenant 1' par 'Enquêté P1' ou 'M. Martin') et met à jour les futurs exports Word (.docx).

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": {
      "file_id": "<file_id>",
      "old_speaker": "<old_speaker>",
      "new_speaker": "<new_speaker>"
    },
    "name": "rename_speaker_label"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_idYesIdentifiant unique de la transcription.
new_speakerYesNouveau nom ou code d'intervenant (ex: 'Enquêté P1', 'Mme Dubois').
old_speakerYesNom actuel de l'étiquette d'intervenant à remplacer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent and non-destructive, and the description adds the key operational fact that the rename applies to every speech turn, not one occurrence, plus that future .docx exports pick up the change (implying already-generated exports are not retroactively changed). It still does not say what happens if old_speaker is not found or what the call returns.

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?

A single front-loaded sentence with the scope and side effect stated up front, and the example in parentheses earns its place by disambiguating the labels. Nothing is redundant with the name or annotations.

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 three-required-parameter mutation with no output schema and full schema descriptions, the definition covers scope, semantics of the replacement, and the export consequence. The remaining gap is error/not-found behavior and confirmation of what the response contains.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description adds real meaning by giving a concrete before/after mapping which clarifies that old_speaker is an existing diarization label while new_speaker is a free-form name or code. It does not add format constraints (length, allowed characters) beyond the schema.

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?

Names a specific verb (renomme) and resource (étiquette d'un intervenant / diarisation) and states the scope: globally across all its speech turns. It also notes the side effect on Word exports, which separates it from the read-only get_* and search_* siblings.

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 parenthetical example of replacing 'Intervenant 1' with a real name, so an agent can infer the intended scenario. But there is no explicit when-to-use, no prerequisites (e.g. transcript must exist), and no guidance on alternatives or what to do if the label is absent.

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

All Le Scribe Audio — Transcription Audio & Vidéo (FR) 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