Skip to main content
Glama

get_transcript

Read-onlyIdempotent

Retrieve the transcript for a named or latest recording, waiting up to a specified time while it is still processing.

Instructions

Transcript of a recording ("latest" or the folder name), waiting up to wait_seconds if it is still running.

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": "get_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
recordingNolatest
wait_secondsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuine value by disclosing blocking behavior (it waits up to wait_seconds while a recording runs). It does not say what happens on timeout or whether a partial transcript is returned.

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?

A single tight sentence with the key semantics front-loaded and no filler. The opening fragment ('Transcript of a recording') is slightly elliptical but efficient.

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?

An output schema exists, so return values needn't be described, and the tool has only two optional parameters. Still missing is what an agent most needs for a blocking call: behavior on timeout and how this differs from get_live_transcript.

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?

With 0% schema description coverage, the description carries the burden and largely does: it explains that 'recording' accepts "latest" or a folder name, and that wait_seconds bounds how long the call blocks. Only the timeout/fallback behavior of wait_seconds is left unstated.

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?

States a specific resource and action: fetching the transcript of a recording. The parenthetical clarifies accepted identifiers, which is helpful. It stops short of distinguishing itself from the close sibling get_live_transcript, so an agent must infer which to use.

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 clause 'waiting up to wait_seconds if it is still running' implies this tool is for in-progress or just-finished recordings, but no explicit when/when-not or alternative (e.g. get_live_transcript, transcribe_file) is named. Usage is inferable but not stated.

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