Skip to main content
Glama

Video File Transcription Price

video_file_transcription_price

Calculate price for video file transcription.

Quotes an uploaded video file by its length. For a URL use video_url_transcription_price.


Available models:

  • WhisperLargeV3Ct2: ts_level: segment|word, diarize, output=json (text + segments)

  • WhisperLargeV3: ts_level: segment

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": "video_file_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 video in seconds, which the price follows

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description carries the full load. It discloses that the tool only quotes ('Calculate price', 'Quotes') and details per-model capabilities, but never states that no job is created and nothing is charged, nor any auth/credit requirements or whether the quote is static or expiring. The capability list is useful behavioral context, but the cost-bearing semantics are left implicit.

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?

Front-loaded with the purpose, then the file-vs-URL fork, then the model reference block. Every sentence earns its place and the delimited model list is easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, so return values needn't be explained, and all six parameters are documented in the schema. What remains missing for a pricing tool with zero annotations is the commercial contract: that this is a quote-only call that starts no processing and incurs no charge, plus currency/unit expectations for the returned price.

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 description coverage is already 100%, so the baseline is 3. The description adds the authoritative model list with each model's supported ts_level, diarize and output shape, which is the reference the schema's 'from the model list' clause points at, so it genuinely supplements the schema rather than repeating it.

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?

States a specific verb and resource ('Calculate price for video file transcription') and immediately scopes it to an *uploaded file* by length, which cleanly separates it from the URL-based sibling. An agent can distinguish it from video_file_transcription and video_url_transcription_price without opening any schema.

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

Usage Guidelines4/5

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

Explicitly routes URL inputs to video_url_transcription_price, which is the main fork an agent faces here. It does not discuss when to use the price tool versus actually running video_file_transcription (e.g. quote first, then transcribe), so the guidance is clear but not complete on lifecycle ordering.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.