Skip to main content
Glama

stop_recording

Idempotent

Stops an active call recording and starts transcription, returning the transcript when ready or telling you to fetch it later.

Instructions

Stop the recording in progress and start its transcription.

speakers: number of people on the other side, if different from the one given at start (0 = unchanged). For a group call, ask the user. language: overrides the language chosen at start. Returns the transcript if it is ready within wait_seconds, otherwise says to call get_transcript later.

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

Input Schema

NameRequiredDescriptionDefault
languageNo
speakersNo
transcribeNo
wait_secondsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare it is a non-destructive, idempotent, non-open-world write, so the bar is lower; the description still adds real behavior — that transcription is launched as a side effect and that the call may return early with a polling instruction. The gap is that it never explains the observable difference when transcribe is set false, which contradicts the flat claim that it 'start[s] its transcription'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The action is front-loaded in the first sentence and the parameter notes follow as terse bullets with no filler. Every line carries information an agent would otherwise have to guess.

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?

Return behavior is covered (and an output schema exists anyway), so the remaining burden is parameters. With 0% schema coverage across four parameters, leaving transcribe undefined is a material hole for a tool whose whole purpose is producing a transcript.

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 coverage is 0%, so the description must carry all parameter meaning. It does explain speakers (0 = unchanged) and language (overrides the start-time choice), and wait_seconds is referenced implicitly, but the transcribe boolean — the most consequential parameter — is never mentioned.

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 verb and resource: stop the in-progress recording and kick off transcription. It is distinguishable from start_recording and get_transcript, but never contrasts itself with the sibling transcribe_recording, which overlaps on the transcription part.

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?

Gives a concrete routing rule ('Returns the transcript if it is ready within wait_seconds, otherwise says to call get_transcript later') and an interactive instruction ('For a group call, ask the user') for speakers. No explicit precondition such as 'only valid while a recording is active', and no contrast with transcribe_recording.

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