Skip to main content
Glama

transcribe_voice

Transcribe audio files or live mic recordings offline with faster-whisper. Capture results as ideas, journal entries, or notes while keeping all data on your machine.

Instructions

Transcribe an audio file or live mic recording and optionally capture the result.

Uses faster-whisper locally — entirely offline, no API calls, no data leaves
your machine. Supports MP3, WAV, M4A, OGG, FLAC, and most other audio formats.

Args:
    audio_path: Path to an audio file to transcribe. Leave empty when using
                record_seconds for live mic capture.
    route_to:   What to do with the transcript after transcription:
                - "raw"     → return the transcript text only (default)
                - "idea"    → capture as an idea with cross-pollination
                - "journal" → add as a journal entry (mood + energy auto-extracted)
                - "note"    → append to today's voice-notes markdown file
    record_seconds: Seconds to record from the microphone. Requires sounddevice
                    and numpy. Only used when audio_path is empty.
    model_size: faster-whisper model size. Options: "tiny", "base", "small",
                "medium", "large-v3". Defaults to METIS_WHISPER_MODEL env var,
                or "base". Larger models are more accurate but slower to load.

Returns:
    The transcript text and (if routed) confirmation of where it was saved.

Examples:
    transcribe_voice(audio_path="/tmp/idea.m4a", route_to="idea")
    transcribe_voice(audio_path="/tmp/reflection.mp3", route_to="journal")
    transcribe_voice(audio_path="", record_seconds=30, route_to="idea")
    transcribe_voice(audio_path="/tmp/note.wav", route_to="note")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
audio_pathNo
route_toNoraw
record_secondsNo
model_sizeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations exist, so the description carries full burden. It discloses local offline processing, supported formats, model size options, routing behavior, and default env var. Lacks detail on performance or error handling but is adequate.

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?

Well-structured with purpose, context, Args, Returns, and Examples. Every sentence adds value. No redundancy. Appropriate length for the information conveyed.

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

Completeness5/5

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

Given 4 parameters, no required params, and an output schema, the description is complete: covers all parameters, behavior, use cases, and examples. Output schema exists and description also mentions return format.

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?

Despite 0% schema coverage, the description explains each parameter in the 'Args' section: audio_path (empty for live mic), route_to (with options), record_seconds (requires dependencies), model_size (with defaults). Adds significant meaning 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?

The description clearly states 'Transcribe an audio file or live mic recording and optionally capture the result.' It specifies the verb (transcribe) and resource (audio file/mic recording), and hints at local offline processing which distinguishes it from potential siblings like transcribe_recording.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains when to use: for audio files or live mic capture. It provides offline privacy context. However, it does not explicitly state when not to use this tool versus alternatives like transcribe_recording, which would improve clarity.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SVerITG/Metis_PH'

If you have feedback or need assistance with the MCP directory API, please join our Discord server