Skip to main content
Glama

Audio Transcription Price

audio_transcription_price

Calculate transcription cost from an audio file's length, including timestamp, diarization, or language options, so you can estimate pricing before submitting the file.

Instructions

Calculate price for audio transcription.

Quotes an uploaded audio file by its length. For a URL use video_url_transcription_price or audio_url_transcription_price.

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": {
      "include_ts": "<include_ts>",
      "duration_seconds": "<duration_seconds>"
    },
    "name": "audio_transcription_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the recording as an ISO code, e.g. 'en', 'pl'. Set it whenever you know the language: auto-detection can pick the wrong one, e.g. on short or accented audio. It forces the output language, so a wrong code returns a translation instead of a transcript. Auto-detected when unset
modelNoWhisper model from the model list. Default WhisperLargeV3Ct2: honours lang, returns segments, supports diarize and word timestampsWhisperLargeV3Ct2
diarizeNoLabel who is speaking; implies include_ts. Only on models marked 'diarize' in the model list (WhisperLargeV3 rejects it). Costs 1.5x, not stacked with a finer ts_level
ts_levelNoTimestamp granularity: 'segment', 'word' or 'char'; implies include_ts. Only the levels a model lists under 'ts_level' in the model list are accepted (WhisperLargeV3: segment only). Finer than segment costs 1.5x on models that price it
include_tsYesInclude timestamps
duration_secondsYesLength of the audio in seconds, which the price follows

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.3

TDQS

A4.2/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 burden; it does disclose that the quote tracks audio length and applies only to uploaded files. It says nothing about whether model/timestamp/diarization choices change the quoted price, which is the main behavioral question for a pricing tool, and the operator multipliers live only in the schema.

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?

Three short sentences, front-loaded with the core purpose and followed immediately by the disambiguation rule. No filler and nothing repeated from the schema.

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?

An output schema exists and the input schema is fully annotated, so return-shape explanation is unnecessary. The description covers scope and sibling routing; only the pricing impact of optional parameters is left implicit, which is minor given the schema coverage.

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 every parameter including lang, model, diarize and ts_level is already documented in the schema with pricing multipliers. The description adds only that price follows duration and does not embellish any other parameter's meaning, so baseline 3 applies.

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?

Specific verb+resource ('Calculate price for audio transcription') immediately narrowed to a scope: 'Quotes an uploaded audio file by its length.' It explicitly separates this tool from the URL-based pricing siblings, which is exactly the distinction an agent needs.

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?

States the selecting condition (uploaded file, length-based quote) and names the alternatives to use for URL inputs ('video_url_transcription_price or audio_url_transcription_price'). This is a direct routing rule, not an implied one.

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