Skip to main content
Glama

obsbot_tail2_exposure

Read or set the OBSBOT Tail 2 camera exposure in auto or manual mode, including face-priority AE, EV bias, ISO, and shutter speed.

Instructions

Read (bare call) or set the Tail 2's exposure. mode manual|auto; in AUTO: face (face-priority AE, global|face) and evbias (-3.0..3.0, ~0.3 steps); in MANUAL: iso (100-6400) and shutter ("1/N", 1/6400..1/30). Manual values only exist in manual mode and face/evbias only in auto — a bare call reports whichever set the current mode exposes. Note: the camera's manual ISO granularity is finer than the doc claims (a live-AE value like 894 reads back).

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_exposure"
  }
}

Input Schema

NameRequiredDescriptionDefault
isoNo
faceNo
modeNo
cameraNo
evbiasNo
shutterNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.9.6
    • removedInput schema / properties / evbias / allOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "maximum": 3,
      -    "minimum": -3,
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / evbias / maximum
      Added value: +3
    • addedInput schema / properties / evbias / minimum
      Added value: +-3
    • addedInput schema / properties / evbias / type
      Added value: +"number"
    • removedInput schema / properties / iso / allOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "maximum": 6400,
      -    "minimum": 100,
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / iso / maximum
      Added value: +6400
    • addedInput schema / properties / iso / minimum
      Added value: +100
    • addedInput schema / properties / iso / type
      Added value: +"number"
  2. Addedv0.9.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the non-obvious read-without-args behavior and per-mode parameter validity, but says nothing about permissions, persistence across restarts, error behavior when mixing modes, or what a bare call returns.

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

Conciseness4/5

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

Front-loaded with the read/write distinction, then mode-scoped parameter detail in a compact, ordered form. The closing note on ISO granularity is a real-world quirk worth keeping, though it is somewhat incidental and one clause could be trimmed.

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?

No output schema and no annotations means the description must be self-sufficient, and it largely is: it explains the bare-call read, the two modes, which parameters are valid in each, ranges, and readback behavior. Only the 'camera' parameter is left unexplained, which is minor for a 6-param tool with zero required fields.

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?

With 0% schema description coverage, the description does the heavy lifting: it documents mode values, iso range 100-6400, shutter format 1/N with 1/6400..1/30 bounds, evbias -3.0..3.0 in ~0.3 steps, and mode-conditional applicability. Gaps remain: the 'camera' parameter is never mentioned, and 'face (face-priority AE, global|face)' is confusing against the boolean schema type.

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 ('Read (bare call) or set the Tail 2's exposure') and makes the dual read/write nature explicit, which is unusual and valuable. It doesn't name the overlapping siblings (obsbot_image_exposure_manual, obsbot_image_exposure_auto, obsbot_tail2_image_adjust), so the agent still has to infer which exposure tool 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 Guidelines3/5

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

It implies usage well: a bare call reads, supplying mode-scoped params writes, and manual fields only apply in manual mode while face/evbias only apply in auto. There is no explicit when-to-use-this-vs-alternative guidance, and the many exposure-related siblings go unmentioned.

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