Skip to main content
Glama

Stop Recording

stop_recording
Idempotent

End an active recording gracefully to finalize the video file and return its path and duration, using the session ID from the recording start.

Instructions

Stop a recording gracefully so the file is finalized; returns the path and duration.

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": {
      "sessionId": "<sessionId>"
    },
    "name": "stop_recording"
  }
}

Input Schema

NameRequiredDescriptionDefault
saveNoReplay buffer: write it all to outputPath first (default: discard).
sessionIdYesSession id returned by start_recording.

Output Schema

NameRequiredDescriptionDefault
statusYes
sessionIdYes
outputPathYes
durationSecYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.47.0
    • addedInput schema / properties / save
      Added value: +{
      +  "description": "Replay buffer: write it all to outputPath first (default: discard).",
      +  "type": "boolean"
      +}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "durationSec": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "outputPath": {
      +      "type": "string"
      +    },
      +    "sessionId": {
      +      "type": "string"
      +    },
      +    "status": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "sessionId",
      +    "status",
      +    "outputPath",
      +    "durationSec"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.32.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), and the description adds that stopping is graceful and finalizes the file. It does not address whether buffered/in-progress data can be lost, which is the main behavioral risk for a stop operation, so it is useful but not rich.

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?

A single tight sentence with the action and the key consequence front-loaded; nothing wasted, nothing buried.

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?

With only two well-described parameters, an output schema covering return values, and annotations covering the safety profile, the definition gives an agent enough to invoke it correctly. The only missing element (stop vs pause guidance) is minor given the sibling names.

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 100% and both parameters (sessionId, save) are documented in the schema, so baseline 3 applies. The description adds no meaning about the save/discard behavior or sessionId expectations beyond what the schema already provides.

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 a recording") plus the outcome ("file is finalized"), which implicitly separates it from pause_recording/resume_recording. It stops short of naming a sibling explicitly, so it is clear but not maximally differentiated.

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?

Usage is only implied by the effect (finalize the file); there is no statement of when to stop versus pause, whether stopping requires an active session, or what happens if the session is already stopped.

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