Skip to main content
Glama
hedging8563

TokenLab MCP Server

by hedging8563
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Create transcription

transcribe_audio

Convert audio files to text using speech-to-text; specify model, language, and output format like JSON, SRT, or VTT.

Instructions

Transcribes audio into text (Speech-to-Text).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileYesAudio file to transcribe Pass local file path.
modelYesModel to use (whisper-1)
promptNoOptional prompt text
languageNoISO-639-1 language code
temperatureNoSampling temperature
response_formatNoResponse formatjson
timestamp_granularitiesNoTimestamp granularity selection. Requires verbose_json output when requesting word-level timestamps.
X-TokenLab-Delivery-PolicyNoPer-request Delivery policy. Overrides the API key and Workspace defaults. Auto tries TokenLab Veri…

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.24
    • addedInput schema / properties / X-TokenLab-Delivery-Policy
      Added value: +{
+  "description": "Per-request Delivery policy. Overrides the API key and Workspace defaults. Auto tries TokenLab Veri…",
+  "enum": [
+    "auto",
+    "verified",
+    "official"
+  ],
+  "type": "string"
+}
  2. Changed1 schema field changedv0.6.4
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  3. Addedv0.3.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, covering the safety profile. The description adds nothing beyond that – no mention of cost, file size limits, latency, or that the call is non-idempotent and may re-bill on retry – so it earns little credit beyond the structured hints.

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?

A single short sentence with the purpose front-loaded and zero filler. It is not padded, though it is arguably terse to the point of under-specification rather than optimally structured.

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?

For a tool with eight parameters, two enums, a hidden Delivery-Policy header, and no output schema, one sentence is insufficient. It never explains the required file/model pairing, the response_format implications, or the timestamp_granularities/verbose_json coupling, leaving the agent to reconstruct these from schema text alone.

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 description coverage is 100%, so all eight parameters including the enums and the verbose_json dependency for timestamp_granularities are documented in the schema itself. The description adds no parameter-level meaning, so the baseline 3 applies.

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 ('Transcribes audio into text') with the domain clarified as Speech-to-Text, so the core action is unambiguous. However, it offers no differentiation from the sibling translate_audio tool, which a naive agent could easily confuse with transcription.

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

Usage Guidelines2/5

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

The description provides no when-to-use guidance, no prerequisites (e.g., that the audio must first be uploaded or a local path supplied), and never mentions the alternative translate_audio tool. The agent must infer everything about selection from the tool name alone.

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

Deploy Server

Other Tools