Skip to main content
Glama
hedging8563

TokenLab MCP Server

by hedging8563
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Translate audio

translate_audio

Transcribe local audio files and translate the resulting text to English, converting non-English recordings into readable English transcripts.

Instructions

Transcribes audio and translates the result to English.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileYesPass local file path.
modelNowhisper-1
promptNo
temperatureNo
response_formatNo
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.7/5.0
Behavior2/5

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

Annotations already cover the safety profile (destructiveHint=false, idempotentHint=false, openWorldHint=true), lowering the bar, but the description adds only that output is English. It says nothing about supported source languages, return format, rate limits, or how the delivery-policy header affects behavior.

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 front-loaded sentence with no filler or redundancy. It is appropriately sized for the thought it contains, though the brevity is partly under-specification rather than precision.

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 six-parameter tool with no output schema, the description omits essential context: what the translation returns, what response_format values do, how prompt/temperature influence results, and which source languages are supported. It is far too thin for the tool's actual complexity.

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

Parameters2/5

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

Schema coverage is only 33%; model, prompt, temperature, and response_format have no schema descriptions, and the description supplies none either. The one documented parameter (file) and the enum'd delivery policy carry all the meaning, so the description fails to compensate for the coverage gap.

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 states a specific compound action on a specific resource: transcription of audio plus translation of the result to English. This distinguishes it functionally from siblings like transcribe_audio and translate_text, but it never names those siblings to make the routing explicit.

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?

There is no when-to-use or when-not-to-use guidance. With siblings transcribe_audio and translate_text present, the agent is left to infer that this tool is the combined one-step path rather than using the two siblings in sequence.

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