Skip to main content
Glama

obsbot_tail2_wb

Read or set the OBSBOT Tail 2 white balance mode and Kelvin temperature from 2000 to 10000K, applying temperature only in manual mode for accurate color under any lighting.

Instructions

Read (bare call) or set the Tail 2's white balance: mode auto|daylight|fluorescent|tungsten|cloudy|manual, plus temperature in Kelvin (2000-10000) which applies in manual mode.

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

Input Schema

NameRequiredDescriptionDefault
modeNo
cameraNo
temperatureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.9.6
    • removedInput schema / properties / temperature / allOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "maximum": 10000,
      -    "minimum": 2000,
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / temperature / maximum
      Added value: +10000
    • addedInput schema / properties / temperature / minimum
      Added value: +2000
    • addedInput schema / properties / temperature / type
      Added value: +"number"
  2. Addedv0.9.0

TDQS

A3.5/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 important behavioral duality (no args = read, args = write) and the mode-dependent applicability of temperature. It omits whether changes persist across sessions, whether writes are rejected outside manual mode, and what a read returns, leaving meaningful behavioral gaps for a device-mutating tool.

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?

A single front-loaded sentence that leads with the read/write duality and the resource before the details. Slight redundancy in re-listing the enum values already encoded in the schema, but no padding or wasted clauses.

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?

With no annotations and no output schema, the description must cover both safety profile and return semantics, and it only partly does — read-vs-write behavior is covered but nothing is said about what a read yields or about preconditions. For a 3-parameter hardware-control tool, one parameter ('camera') and the response shape remain undocumented.

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?

Schema coverage is 0%, so the description must compensate: it enumerates the valid mode values and gives the Kelvin range, and crucially adds the dependency semantics that temperature only takes effect in manual mode — meaning not present in the schema. The 'camera' parameter remains entirely unexplained in both schema and description, which keeps this from a 5.

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 states a specific verb+resource pair ('Read (bare call) or set the Tail 2's white balance') and names the controllable values, so an agent can tell exactly what the tool touches. It does not differentiate itself from the related siblings obsbot_image_wb_auto and obsbot_image_wb_manual, which also deal with white balance, so the sibling-disambiguation bonus is not earned.

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?

Usage is implied rather than spelled out: 'bare call' signals the read path and the note that temperature 'applies in manual mode' is a genuine conditional guideline. However, it never says when to prefer this tool over the white-balance siblings or whether setting a mode requires the camera to be awake/connected, so guidance stops short of explicit alternatives.

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