Skip to main content
Glama

DeepSeek ASR

deepseek_asr

Transcribe local 16-bit PCM WAV or Ogg Opus audio files with DeepSeek's ASR API for speech-to-text, limited to 8 MiB and 120 seconds.

Instructions

Transcribe a local WAV (16-bit PCM) or Ogg Opus audio file with DeepSeek's ASR API. Max 8 MiB / 120 seconds.

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_path": "<file_path>"
    },
    "name": "deepseek_asr"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesLocal path to a 16-bit PCM WAV or Ogg Opus file. Max 8 MiB and 120 seconds; stereo is transcribed from the left channel only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose two meaningful behavioral constraints (8 MiB / 120 s cap, left-channel-only stereo handling), but says nothing about permissions, latency, failure behavior, or what the call returns, which are the main open questions for a transcription call.

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?

Two short sentences, front-loaded with the action and resource, with the hard constraints stated immediately. Nothing is redundant or padded.

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?

For a single-parameter, non-mutating tool with full schema coverage, the definition covers the essentials: what it does, accepted formats, and hard limits. The remaining gap is the return value (no output schema), though the result of a transcription call is largely self-evident.

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

Parameters3/5

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

Schema coverage is 100% and there is only one parameter, so the schema already documents file_path fully. The description restates the same format/size constraints rather than adding new meaning, which matches the baseline-3 expectation when the schema does the work.

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 ... audio file") plus the supported formats and the backing API (DeepSeek ASR). It is clearly distinguishable from siblings such as deepseek_ocr or deepseek_tts by modality, though it never names a sibling or explicitly contrasts with them.

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 format and size/duration limits imply when the tool is usable (short local audio in exactly two codecs), which is useful context. However, there is no explicit when-to-use vs. when-not guidance, and no mention of what to do if the file is too large or in another format.

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