Skip to main content
Glama

transcribe_file

Transcribe existing audio or video files locally, separating multiple speakers and generating text transcripts for meetings, voice notes, or recordings.

Instructions

Transcribe an existing audio or video file (WhatsApp voice note .opus, .m4a, .mp3, .mp4, meeting recording...), copied into a new recording folder.

speakers: total number of people speaking in the file (above 1, their voices are separated into Speaker 1, Speaker 2...).

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": {
      "path": "<path>"
    },
    "name": "transcribe_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
titleNo
languageNo
speakersNo
wait_secondsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior4/5

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

Annotations declare this is a non-read-only, non-destructive, non-idempotent operation, and the description adds real value beyond them: it discloses the side effect that the source file is copied into a new recording folder, and it explains diarization behavior via the speakers note. It does not disclose whether the call blocks or returns immediately, which is the main remaining behavioral unknown.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose sentence is front-loaded and the format examples are concrete, but the trailing 'meeting recording...' ellipsis list is loose filler and the speakers note is set off as a dangling fragment rather than integrated text. Nothing is grossly verbose, but the structure is ragged.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need no explanation, but the description omits the single most consequential fact for an agent: whether transcription is synchronous or must be polled, given wait_seconds defaults to 30 and siblings get_transcript and recording_status exist. For a 5-parameter tool with 0% schema coverage, this gap leaves the call protocol underspecified.

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 coverage is 0% across 5 parameters, yet the description only explains 'speakers' (values above 1 trigger diarization into Speaker 1, Speaker 2). The critical parameters path, title, language, and especially wait_seconds are left entirely undefined in both schema and description, so the description does not compensate for the coverage 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 specific verb and resource ('Transcribe an existing audio or video file') and enumerates concrete input formats (.opus, .m4a, .mp3, .mp4), which makes the tool's scope unambiguous. It does not name or contrast with the sibling transcribe_recording, so an agent must infer the difference from the 'existing file copied into a new recording folder' phrasing rather than being told.

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 only implied: the 'existing file ... copied into a new recording folder' framing suggests importing an external file, which hints at when to prefer this over transcribe_recording. No explicit when-to-use, when-not-to-use, or prerequisite (e.g. copy must complete first) is stated.

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