Skip to main content
Glama

TranscriptLab

Transcribe an audio file

transcriptlab_open_audio

Entry point the host invokes when the user opens an audio or video file with this plugin: opens the uploader view and starts speech-to-text. You do not call this directly; for a file attached to the conversation use transcriptlab_transcribe_file.

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": "<file>"
    },
    "name": "transcriptlab_open_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesHost-provided handle for the opened file.
diarizeNoLabel speakers; defaults to false. Implies tier=premium and 10 credits per audio minute.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare a non-read-only, open-world, non-destructive operation, and the description adds the key behavioral fact beyond them: the call is host-triggered and produces a UI view plus a transcription start. It stops short of saying what happens on a second invocation or what the tool returns, so it is not fully exhaustive.

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 sentences, no filler, and the disallowed-usage instruction is front-loaded alongside the alternative so an agent cannot miss it before reading 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?

For a host-invoked entry point with a fully documented schema and no output schema, the definition covers what the agent needs: what it triggers and who should call it instead. A note on what the UI view expects after opening, or behavior on repeat calls, would close the remaining gap.

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 both `file` and `diarize` are already documented, including diarize's cost implication (tier=premium, 10 credits per audio minute). The description adds no parameter meaning beyond that, so the 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?

States a specific role — host-invoked entry point that 'opens the uploader view and starts speech-to-text' — and distinguishes itself from the file-attachment path by naming transcriptlab_transcribe_file. An agent can tell immediately this is a UI-opening loader rather than a transcription API call.

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?

Explicitly gives both the when and the when-not: it is what 'the host invokes when the user opens an audio or video file,' and 'You do not call this directly; for a file attached to the conversation use transcriptlab_transcribe_file.' The routing decision is unambiguous.

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.