Skip to main content
Glama

stop_recording

Stop the active video recording on an iOS simulator by terminating the recording process.

Instructions

Stops the simulator video recording using killall

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The 'stop_recording' tool handler that sends SIGINT to kill the simctl recordVideo process and stops the recording.
    if (!isToolFiltered("stop_recording")) {
      server.tool(
        "stop_recording",
        "Stops the simulator video recording using killall",
        {},
        { title: "Stop Recording", readOnlyHint: false, openWorldHint: true },
        async () => {
          try {
            await run("pkill", ["-SIGINT", "-f", "simctl.*recordVideo"]);
    
            // Wait a moment for the video to finalize
            await new Promise((resolve) => setTimeout(resolve, 1000));
    
            return {
              isError: false,
              content: [
                {
                  type: "text",
                  text: "Recording stopped successfully.",
                },
              ],
            };
          } catch (error) {
            return {
              isError: true,
              content: [
                {
                  type: "text",
                  text: errorWithTroubleshooting(
                    `Error stopping recording: ${toError(error).message}`
                  ),
                },
              ],
            };
          }
        }
      );
  • src/index.ts:1061-1098 (registration)
    Registration of the 'stop_recording' tool on the MCP server, guarded by a filter check.
    if (!isToolFiltered("stop_recording")) {
      server.tool(
        "stop_recording",
        "Stops the simulator video recording using killall",
        {},
        { title: "Stop Recording", readOnlyHint: false, openWorldHint: true },
        async () => {
          try {
            await run("pkill", ["-SIGINT", "-f", "simctl.*recordVideo"]);
    
            // Wait a moment for the video to finalize
            await new Promise((resolve) => setTimeout(resolve, 1000));
    
            return {
              isError: false,
              content: [
                {
                  type: "text",
                  text: "Recording stopped successfully.",
                },
              ],
            };
          } catch (error) {
            return {
              isError: true,
              content: [
                {
                  type: "text",
                  text: errorWithTroubleshooting(
                    `Error stopping recording: ${toError(error).message}`
                  ),
                },
              ],
            };
          }
        }
      );
    }
  • Schema definition: the tool takes no parameters (empty object) and has a description about stopping recording using killall.
    "stop_recording",
    "Stops the simulator video recording using killall",
    {},
  • Helper 'run' function used to execute pkill to stop the recording process.
    async function run(
      cmd: string,
      args: string[],
      options: RunOptions = {}
    ): Promise<{ stdout: string; stderr: string }> {
      const mergedEnv = options.env
        ? { ...process.env, ...options.env }
        : process.env;
      const { stdout, stderr } = await execFileAsync(cmd, args, {
        shell: false,
        env: mergedEnv,
      });
      return {
        stdout: stdout.trim(),
        stderr: stderr.trim(),
      };
    }
Behavior5/5

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

Adds 'using killall' beyond annotations, revealing forceful termination. No contradiction with annotations.

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?

Single sentence with no wasted words. Every phrase earns its place.

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 zero-parameter tool with no output schema, the description fully covers the action and mechanism. No gaps.

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?

No parameters, schema coverage 100%. Description adds no param info but doesn't need to; baseline 4 applies.

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?

Clearly states it stops simulator video recording using killall, distinguishing it from record_video and other sibling tools.

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?

While it's obvious as the counterpart to record_video, the description doesn't explicitly mention when to call it or prerequisites like 'only if recording is active'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/joshuayoes/ios-simulator-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server