Skip to main content
Glama

TranscriptLab

Read uploaded-audio transcript

transcriptlab_read_audio_transcript
Read-only

Read the transcript of a file uploaded through the uploader view. A pending transcription reports 202; retry shortly. App-facing only.

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": {
      "upload_id": "<upload_id>"
    },
    "name": "transcriptlab_read_audio_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNo
upload_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the description's job is to add operational context and it does: a pending transcription returns 202 and should be retried shortly, and the tool is app-facing only. What is missing is any statement of what is returned or how the requested format affects the response.

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?

Three short sentences, front-loaded with purpose, then the failure mode, then the audience restriction. Nothing is redundant, though 'App-facing only' is terse enough to be slightly ambiguous without elaboration.

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?

There is no output schema, so the description should convey what a successful read yields and how the format option changes it; it says neither. Combined with the complete absence of documented parameters, the definition is callable but leaves real gaps for a two-parameter, multi-format reader.

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 description coverage is 0% across two parameters, so the description must carry the burden. It only hints that upload_id refers to a file uploaded via the uploader view; the format parameter and its four enum values (json/text/srt/vtt) are never mentioned, nor is any format-specific behavior explained.

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?

A clear verb+resource ('Read the transcript') scoped to files 'uploaded through the uploader view', which separates it from the sibling transcript readers that operate on other sources. It stops short of naming a specific sibling to contrast with, so differentiation is inferential rather than explicit.

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

Usage Guidelines3/5

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

The 202/retry note and 'App-facing only' establish usage context, but there is no when-to-use versus when-to-use-an-alternative guidance despite many sibling transcript tools. An agent must infer that this is only for uploader-view uploads, not for arbitrary transcript retrieval.

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.