Skip to main content
Glama
smallest-inc

Smallest MCP Server

Official
by smallest-inc

transcribe_audio

Transcribe audio files to text with support for 32+ languages. Specify the language and provide a file path or URL for accurate transcription.

Instructions

Transcribe an audio file to text using Smallest AI's Pulse STT. Supports 32+ languages. IMPORTANT: Always ask the user what language the audio is in before calling this tool. Pass a file path on the user's machine (e.g. ~/Desktop/recording.wav) or a publicly accessible URL. Note: files uploaded to the chat sandbox are NOT accessible — ask the user for the actual file path on their machine or a URL instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathNoPath to audio file on the user's machine (e.g. ~/Desktop/recording.wav, /Users/name/audio.mp3). NOT sandbox paths. Either file_path or audio_url is required.
audio_urlNoPublicly accessible URL of an audio file. Either file_path or audio_url is required.
languageYesLanguage of the audio. REQUIRED — ask the user. Use ISO 639-1 codes: en, hi, es, de, fr, it, pt, ta, mr, gu, bn, kn, ml, te, pa, or, ru, uk, pl, nl, sv, etc. Use 'multi' only if the user explicitly says they don't know the language.
word_timestampsNoInclude word-level timestamps with confidence scores
diarizeNoEnable speaker diarization (identify different speakers)
emotion_detectionNoDetect emotions in speech
redact_piiNoRedact personally identifiable information from transcription
Behavior4/5

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

Disclosure includes tool provider, language support, and input requirements. No annotations provided, so description carries full burden; it covers key behavioral aspects but lacks details on output format or rate limits.

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?

Concise but informative, front-loaded with purpose, then critical usage notes. Every sentence adds necessary context without redundancy.

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?

Covers all essential aspects: purpose, input methods, language requirement, and feature flags. No output schema, so return value omitted, but overall sufficient for this tool's complexity.

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%, baseline 3. Description adds value by providing concrete examples for file_path and audio_url, and reinforcing language requirement with ISO codes. Other parameters rely on schema which is clear.

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?

Clearly states 'Transcribe an audio file to text' using Smallest AI's Pulse STT. Specific verb and resource, no sibling overlaps, so differentiation is inherent.

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

Usage Guidelines5/5

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

Explicitly instructs to ask user for language, warns against using sandbox paths, and distinguishes between file path and URL usage. Clear when-to-use and what to avoid.

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/smallest-inc/mcp-server'

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