Skip to main content
Glama

stop_recording

Stops an active recording, flushes pending frames, writes metadata with simulation times, and returns frame count, duration, and session details.

Instructions

Stop the running recording: wait for the frames still being written, write metadata.json with each frame's simulation time, and hand the render back to the captures, kept up to 30 s unless a capture's render is still kept at the stop, which stays instead.

Returns the frame count, the duration, the seconds of simulation played and the seconds stopped or paused (the frame count comes out near fps times their sum), the session folder and the state file, with a note when frames stopped early or the cleanup failed in part. An error when no recording runs. Use get_recording_frame to review frames.

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

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only flag it as a non-read-only, non-destructive, closed-world write; the description adds substantial context on top: it blocks until in-flight frames are flushed, writes metadata.json, returns render control with a 30 s grace period unless a capture still holds the render, and surfaces partial-failure notes. That is exactly the mutation behavior an agent needs before invoking it.

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

Conciseness3/5

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

The lead sentence is well front-loaded, but the render-handback clause ("hand the render back to the captures, kept up to 30 s unless a capture's render is still kept at the stop, which stays instead") is tangled and hard to parse on first read. The lengthy enumeration of return fields is also partly redundant because an output schema exists.

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 zero-parameter mutation with annotations and an output schema, the description covers effects, failure modes, and the follow-up tool. Its remaining weakness is spending effort restating return values that the output schema already documents, while the render-handback rule stays ambiguous.

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?

The tool takes zero parameters, so there is no argument semantics to explain and the baseline is 4. The description does not need to compensate for anything here.

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 ("Stop the running recording") and enumerates its effects: waiting on pending frames, writing metadata.json with per-frame simulation time, and restoring render ownership. This clearly separates it from start_recording and get_recording_frame without opening either 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?

Gives the error condition ("An error when no recording runs") and explicitly routes review work to a sibling: "Use get_recording_frame to review frames." It stops short of stating the obvious pairing with start_recording or any prerequisites for calling it, so it is clear but not fully exhaustive.

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