Skip to main content
Glama

aw.speech.transcript.clear

Destructive

Explicitly clear the EXPECTED CURRENT shared transcript only and leave an empty generation, matching original Clear semantics. Null succeeds only when no current state exists; a stale handle cannot clear a newer result. Does NOT cancel in-flight transcription, selected input, encoder/pending state, or previously downloaded immutable exports. A later valid model completion may populate the transcript again. Exact UUID replay must still refer to the same cleared generation. Removes active private encrypted snapshot, NOT irreversible provider backups/E2EE; no new model/device I/O.

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

Input Schema

NameRequiredDescriptionDefault
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

A4.2/5.0
Behavior3/5

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

Annotations already declare destructive=true and readOnly=false, so the mutation profile is known. The description adds genuinely non-obvious behavior beyond that: null succeeds only with no current state, stale handles cannot clear newer results, exact UUID replay must map to the same cleared generation, and it removes a private encrypted snapshot but not provider backups/E2EE. It's strong added context, but several clauses are cryptic enough that the practical effect is good rather than excellent.

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 action and its scope before the caveats, and every clause carries a distinct constraint rather than restating the name. It is dense and jargon-laden ('immutable exports', 'E2EE'), which costs some readability but no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter destructive mutation with no output schema, the description covers safety-relevant behavior (what is destroyed, what is not, replay semantics, no new model/device I/O) that an agent needs before calling it. Nothing essential to correct invocation is missing.

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 described), so the description must compensate and largely does: 'Null succeeds only when no current state exists' explains the nullable transcript, and 'Exact UUID replay must still refer to the same cleared generation' explains operationId's idempotency contract. Remaining gap is that these are stated as invariants rather than per-parameter guidance.

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 ('clear the EXPECTED CURRENT shared transcript') plus the resulting state ('empty generation'), and the 'EXPECTED CURRENT ... only' scope phrase separates it from clearing stale or in-flight work. An agent can distinguish this from aw.speech.transcript.read/export and from cancellation tools 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 Guidelines4/5

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

Explicitly enumerates what this is not for ('Does NOT cancel in-flight transcription, selected input, encoder/pending state, or previously downloaded immutable exports'), which steers the agent away from misuse. It stops short of naming the tool to use instead for cancellation, so it is clear context without full alternative routing.

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