Skip to main content
Glama
Sign In

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

by io.github.zoulouzaza76
OverviewDiscussionsAdmin

get_transcription_text

Read-onlyIdempotent

Récupère le texte intégral diarisé (par intervenant, avec timecodes optionnels [HH:MM:SS]) d'une transcription appartenant à l'utilisateur.

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>"
    },
    "name": "get_transcription_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_idYesIdentifiant unique de la transcription (issu de list_transcriptions).
max_charsNoLimite de caractères retournés (1000 à 200000, défaut 60000).
offset_charsNoDécalage en caractères pour lire la suite des très longues séances (défaut 0).
include_timecodesNoInclure les horodatages [HH:MM:SS] devant chaque prise de parole.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds diarization behavior (text grouped per speaker with optional [HH:MM:SS] timecodes) that is beyond annotations, but says nothing about truncation behavior when max_chars is exceeded.

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?

A single front-loaded sentence naming the verb and the key qualifiers (diarized, per speaker, optional timecodes). Dense but every word earns its place; only minor readability cost from packing everything into one clause.

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?

A read-only getter with 100% schema coverage and full annotations; the description explains what the content looks like (diarized, optional timecodes). It omits how truncation interacts with max_chars and there is no output schema, but nothing essential for correct invocation is missing.

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

Parameters5/5

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

Schema coverage is 100%, and the description still adds meaning by explaining output layout: text per speaker plus optional [HH:MM:SS] timecodes. The paging parameters are self-explanatory in the schema, so the baseline 3 is exceeded by the diarization/timecode detail.

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 states a specific verb and resource: retrieves the full diarized text of a transcription, with timecodes optional. It distinguishes itself implicitly from get_transcription_summary (full text vs. summary) but never names that sibling, so sibling differentiation is left to inference.

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?

The pointer that file_id comes from list_transcriptions lives in the schema, not the description. The description implies the use case (reading full text) but gives no explicit when-to-use, when-not, or a routing sentence to get_transcription_summary for a condensed view.

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