Skip to main content
Glama

aw.speech.whisper_export_txt

Export the original TXT from a complete current-session SRT produced by aw.speech.whisper_decode_step, without invoking the model again. Only a verified original decoder SRT artifact in the same active source revision is accepted; no imported SRT, other session, stale source, or unfinished state. Keeps the original whole-second timestamps, text and CRLF. Returns a verified immutable authenticated TXT artifact, not inline transcript content. Reuse operationId for the same SRT; inspect the job before an explicit retry.

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>",
      "srt": "<srt>"
    },
    "name": "aw.speech.whisper_export_txt"
  }
}

Input Schema

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

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 only give the generic readOnly=false / destructive=false / openWorld=false profile; the description adds real behavioral context — the source artifact must be verified, the export does not re-invoke the model, timestamps/text/CRLF are preserved verbatim, and the result is an immutable authenticated artifact rather than inline text. It still does not say what happens on a failed verification or how a partial job surfaces, which keeps it below a 5.

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?

Front-loaded with the core action and source, then constraints, then output form, then retry advice — no filler sentences. The final clause ('inspect the job before an explicit retry') is terse and does not name the job-inspection sibling, costing it a point.

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 three-parameter mutation with no output schema, it covers input provenance, fidelity guarantees, and the nature of the return value (an artifact handle, not content). It could be more complete by pointing at how to read the resulting artifact (aw.artifact.read_chunk) or at aw.artifact.verify for the verification step it references.

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 only 33% (only session is documented), but the description compensates by constraining the srt argument to a verified original decoder artifact from the current session/revision, and by explaining operationId's idempotency role. It does not describe the artifact-ID or UUID formats themselves, but those are largely conveyed by the schema patterns.

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 verb and resource ('Export the original TXT from a complete current-session SRT'), names the producing sibling aw.speech.whisper_decode_step, and explicitly distinguishes this from re-running the model. An agent can identify the operation without opening the schema.

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 preconditions and exclusions are spelled out: only a verified original decoder SRT in the same active source revision, and no imported SRT, other session, stale source, or unfinished state. It also gives retry guidance ('reuse operationId for the same SRT; inspect the job before an explicit retry'), which covers both when to call and when not to.

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