Skip to main content
Glama

TranscriptLab

Open TranscriptLab

transcriptlab_open
Read-only

Open the TranscriptLab launcher view, where the user can work with transcripts visually and send one into the chat with "Discuss in chat". Use tab "upload" when a file needs the uploader: the user wants to pick a local audio or video file, the attached file is too large or could not be read by transcriptlab_transcribe_file, or that upload failed. Use "library" to reopen earlier transcripts, and "link" (the default) to paste a YouTube link. Also offer it when the user wants a transcript but has given no link or file.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "transcriptlab_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabNoWhich launcher tab to show first; defaults to link.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly=true, destructive=false, and closed-world, so the safety profile is covered. The description adds behavior annotations don't: this opens a persistent visual view the user then acts in, and transcripts can be pushed into chat from it — meaningful context for an agent deciding whether to invoke it. It stops short of saying whether the agent's turn ends after the view opens.

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 sentences: purpose first, then tab routing, then a fallback trigger — well front-loaded and free of filler. The routing sentence is dense but every clause maps to a distinct condition, so nothing is wasted.

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 one-optional-param, read-only navigation tool with no output schema, the description covers purpose, defaults, and invocation triggers thoroughly. The only gap is post-invocation behavior — what the agent should do or say once the launcher view is open — which is minor for a tool this simple.

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 coverage is 100% and the enum values are already listed, but the description goes further by attaching a decision rule to each value ('upload' for local files/failed reads, 'library' for earlier transcripts, 'link' default for YouTube). That is real semantic value beyond the generic 'which launcher tab to show first' in the schema.

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?

A concrete verb+resource: 'Open the TranscriptLab launcher view', with the tab metaphor and the 'Discuss in chat' handoff explained. It also distinguishes itself from the sibling it names (transcriptlab_transcribe_file), so the agent can tell this is a UI entry point rather than a transcription 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?

Explicit routing for every case: 'upload' when the user wants to pick a local file, the file is too large, transcriptlab_transcribe_file could not read it, or that upload failed; 'library' to reopen earlier transcripts; 'link' as default. It closes with a proactive trigger — offer it when the user wants a transcript but gave no link or file.

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.