Skip to main content
Glama

obsbot_tail2_snapshot

Capture a still frame from an OBSBOT Tail 2 camera via SRT and ffmpeg for framing, lighting, or pixel checks; if SRT is off, returns setup options.

Instructions

Grab one still frame from a Tail 2 and return it as an image (for framing/lighting checks — and for measuring pixels). Source: the camera's SRT output via ffmpeg SRT caller (port 5000) — requires SRT listener mode in OBSBOT Center; exclusive with NDI, cleared by reboots, and Center only allows changing streaming settings while the output is off. Serves immediately once on. If SRT is off, returns a report of what it found with the available options and their costs (SRT toggle, NDI Webcam bridge caveats, NDI Tools install) so you can pick the cheapest path instead of dead-ending. resolution is the longest edge (256–1920, default 640); quality 1–100 (default 80). Needs ffmpeg. Frames are 16:9 1080p-sourced.

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

Input Schema

NameRequiredDescriptionDefault
cameraNo
qualityNo
resolutionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.9.6
    • removedInput schema / properties / quality / allOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "maximum": 100,
      -    "minimum": 1,
      -    "type": "integer"
      -  }
      -]
    • addedInput schema / properties / quality / maximum
      Added value: +100
    • addedInput schema / properties / quality / minimum
      Added value: +1
    • addedInput schema / properties / quality / type
      Added value: +"integer"
    • removedInput schema / properties / resolution / allOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "maximum": 1920,
      -    "minimum": 256,
      -    "type": "integer"
      -  }
      -]
    • addedInput schema / properties / resolution / maximum
      Added value: +1920
    • addedInput schema / properties / resolution / minimum
      Added value: +256
    • addedInput schema / properties / resolution / type
      Added value: +"integer"
  2. Addedv0.9.0

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations, the description carries the whole burden and does so thoroughly: source is the camera's SRT output via ffmpeg SRT caller on port 5000, requires SRT listener mode in OBSBOT Center, is exclusive with NDI, is cleared by reboots, and Center only allows streaming-setting changes while output is off. It also discloses the dependency (ffmpeg) and the degraded-report behavior when SRT is unavailable.

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?

Purpose and output shape are front-loaded in the first clause, then operational prerequisites, then fallback behavior, then parameter notes. Despite covering a lot, every sentence adds a fact an agent needs to call the tool or interpret a failure; the only mild waste is restating schema defaults.

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 tool with no annotations and no output schema, the description covers prerequisites, exclusivity constraints, dependencies, failure behavior, and frame aspect/resolution source. The remaining gaps are the unexplained `camera` parameter and no explicit note on image encoding/return format beyond "return it as an image".

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 compensate. It usefully explains that resolution is the longest edge and that frames are 16:9 1080p-sourced, but the min/max/default values it cites are already in the schema, and the required-in-practice `camera` parameter (type string, no description) is never explained — no identifier format or discovery hint.

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?

Opens with a specific verb and resource: "Grab one still frame from a Tail 2 and return it as an image," plus the intended use (framing/lighting checks, pixel measurement). It does not distinguish itself from near-identical siblings such as obsbot_tail2_capture_photo or obsbot_capture_snapshot, so an agent must guess which capture path to pick.

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 concrete when-to-use context (framing, lighting, measuring pixels) and a clear when-not/dead-end path: if SRT is off it returns a report of options and their costs so the caller can pick the cheapest route. It omits the most relevant comparison, however — no guidance on when to prefer this over the other snapshot/photo siblings.

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

Deploy Server

Other Tools