Skip to main content
Glama

save_screenshot

Capture the current OBS Studio output as an image file in PNG, JPG, or BMP format at a specified file path.

Instructions

Save a screenshot of the current OBS output to a file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYesAbsolute path where the screenshot should be saved (e.g. /tmp/obs-shot.png).
image_formatNoImage format: png, jpg, bmp. Defaults to png.

Implementation Reference

  • Handler implementation for the save_screenshot tool. It uses obs-websocket's SaveSourceScreenshot command to capture the current scene.
    case "save_screenshot": {
      await obs.call("SaveSourceScreenshot", {
        sourceName: (await obs.call("GetSceneList")).currentProgramSceneName,
        imageFormat: args.image_format ?? "png",
        imageFilePath: args.file_path,
      });
      return ok({ saved_to: args.file_path });
    }
  • Tool definition and input schema for save_screenshot.
      name: "save_screenshot",
      description: "Save a screenshot of the current OBS output to a file.",
      inputSchema: {
        type: "object",
        properties: {
          file_path: {
            type: "string",
            description:
              "Absolute path where the screenshot should be saved (e.g. /tmp/obs-shot.png).",
          },
          image_format: {
            type: "string",
            description: "Image format: png, jpg, bmp. Defaults to png.",
          },
        },
        required: ["file_path"],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'current OBS output' clarifies the capture target, critical safety and behavioral details are missing: file overwrite behavior, whether the operation is synchronous, error conditions (invalid paths, disk full), and return value indications.

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 single 11-word sentence is efficiently front-loaded with the action and object. There is no redundancy or wasted space; every word serves a purpose.

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?

Given the absence of an output schema, the description adequately covers the core intent but leaves significant gaps regarding success/failure feedback (since return structure is undefined) and file system safety implications inherent to write operations.

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?

The input schema has 100% description coverage with clear documentation of the file_path and image_format parameters including defaults and examples. The description provides the baseline context ('to a file') but adds no additional semantic detail 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?

The description uses a specific verb ('Save') and resource ('screenshot of the current OBS output'), clearly distinguishing this as an image capture operation versus the video recording functions (start_recording, stop_recording) present in siblings. However, it doesn't explicitly clarify the single-frame nature versus continuous recording.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives (e.g., 'use this for single images instead of start_recording for video'), no prerequisites mentioned (OBS must be running), and no caution about file overwrites.

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/LarsCanGit/OBS-MCP'

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