Skip to main content
Glama

Metis — Transcribe Voice

transcribe_voice

Transcribe audio files or live mic recordings offline. Optionally route transcripts to ideas, journals, or notes for organized capture.

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
route_toNoraw
audio_pathNo
model_sizeNo
record_secondsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description fully discloses offline operation, supported formats, routing behavior, and model size options. It does not mention any destructive side effects, but the 'route_to' parameter implies potential file creation, which is documented.

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?

The description is well-structured with a summary, a note about offline processing, and a clear Args section. It is somewhat verbose but each sentence adds value. Front-loaded with core purpose.

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 the complexity of audio transcription and routing, the description covers inputs, outputs, behavior, and constraints. The return value is described, and examples illustrate common usage. No gaps for an AI agent to correctly invoke the tool.

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 provides thorough parameter documentation: each parameter's purpose, options, defaults, and interactions (e.g., record_seconds used only when audio_path empty). This adds significant value beyond the schema.

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 clearly states 'Transcribe an audio file or live mic recording' with a specific verb and resource. It is distinct enough from siblings like 'transcribe_recording', though it does not explicitly differentiate.

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 description provides examples and explains parameters, but lacks explicit when-to-use or when-not-to-use guidance relative to sibling tools. Usage context is implied rather than stated.

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'

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