Skip to main content
Glama

aw.speech.transcript.export

Export the CURRENT accepted transcript as exact original TXT or SRT, with NO model call. Same original serializers/timestamp fallback/CRLF, verified immutable header-auth artifact. Explicit current handle and UUID; replay requires same current generation/source/settings and actual verified bytes. Nothing to export after Clear/empty; stale/current-source mismatch rejects. A previously downloaded export is not erased by Clear. No browser OS-save/accuracy/backup-erasure claim.

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": {
      "session": "<session>",
      "operationId": "<operationId>",
      "transcript": "<transcript>",
      "output": "<output>"
    },
    "name": "aw.speech.transcript.export"
  }
}

Input Schema

NameRequiredDescriptionDefault
outputYes
sessionYesPrivate short-lived session capability returned by aw.session.open. Never publish or log it.
transcriptYes
operationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations only declare readOnlyHint=false, openWorldHint=false, and destructiveHint=false, and the description adds meaningful behavior beyond them: exact original serializers, timestamp fallback, CRLF preservation, a verified immutable header-auth artifact, and a 'no browser OS-save/accuracy/backup-erasure claim' disclaimer. It also discloses that a previously downloaded export survives Clear, which an agent could not infer from the annotations. The return shape is left unaddressed.

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?

The core purpose is front-loaded in the first clause ('Export the CURRENT accepted transcript as exact original TXT or SRT'), followed by edge cases and disclaimers. The style is dense and telegraphic, but nearly every clause carries distinct information; the closing disclaimer is the weakest-earning sentence.

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?

For a four-parameter, fully-required mutation-adjacent tool with no output schema, the description covers rejection conditions, replay constraints, and Clear interaction well. However, it never says what the call returns (for example, an artifact or byte handle, which the aw.artifact.read_chunk sibling hints at), leaving the agent without a next-step contract.

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 only 25%: only `session` is documented in the schema, and `transcript`, `operationId`, and `output` carry no descriptions. The phrase 'Explicit current handle and UUID' maps loosely to the transcript handle and operationId, and 'TXT or SRT' echoes the output enum, but neither adds format or validation meaning. It only partially compensates for the coverage gap.

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?

The description states a specific verb and resource: 'Export the CURRENT accepted transcript' in 'TXT or SRT', and adds 'NO model call', which implicitly separates it from the whisper export sibling. The scope is clear, but the description never names an alternative tool directly, so the differentiation is inferred rather than stated.

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?

It gives concrete preconditions for use and rejection: 'Nothing to export after Clear/empty; stale/current-source mismatch rejects', and 'replay requires same current generation/source/settings'. The 'with NO model call' phrasing implicitly steers agents away from model-invoking siblings, though no sibling is named explicitly.

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.

Resources