Skip to main content
Glama

obsbot_tail2_image_adjust

Read or set OBSBOT Tail 2 image style—brightness, contrast, hue, saturation, sharpness, and styleMode—while enforcing manual mode before individual control writes.

Instructions

Read (bare call) or set the Tail 2's image style: brightness/contrast/hue/saturation/sharpness, each an absolute 0-100, plus styleMode standard|outdoor|pastel|manual. Individual control writes are MODE-GATED (measured): they apply only in styleMode manual — HTTP 500 "style mode is not manual" otherwise — so this tool applies a given styleMode FIRST and refuses a control write in a preset mode. A styleMode switch preserves the current values. Bare call returns the full style bundle.

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

Input Schema

NameRequiredDescriptionDefault
valueNo
cameraNo
controlNo
styleModeNo

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so: it discloses the measured failure mode (HTTP 500 'style mode is not manual'), the internal ordering behavior (styleMode applied first), the refusal semantics for preset modes, and that a styleMode switch preserves current values. This is exactly the behavioral context an agent needs before issuing a write.

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 duality and the field list, then the constraint. The caps emphasis and '(measured)' aside plus the restated 'refuses a control write in a preset mode' add a little redundancy, but nearly every clause conveys a distinct behavioral fact.

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?

No output schema exists, and the description still tells the agent that a bare call returns the full style bundle. For a mutation-capable tool with no annotations, the key risks (mode gating, ordering, error condition) are all covered; only the camera parameter and the exact shape of the returned bundle are left implicit.

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 description coverage is 0%, so the description must compensate; it explains that value is an 'absolute 0-100' rather than a relative delta, and names all five control values and four styleMode values with their mode-gating consequence. However, the 'camera' parameter — presumably a device selector — is never explained anywhere, leaving one of four parameters undocumented.

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?

States a specific verb pair and resource: 'Read (bare call) or set the Tail 2's image style', then enumerates exactly which controls are covered (brightness/contrast/hue/saturation/sharpness) plus styleMode. Naming the Tail 2 and the exact field set distinguishes it from gimbal, exposure, white-balance and other siblings without needing to name them.

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

Usage Guidelines5/5

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

Explicit when-to-use and when-not-to-use guidance: individual control writes apply only in styleMode manual, the tool applies a supplied styleMode FIRST, and it refuses a control write in a preset mode. It also tells the agent that a bare call is the read path, giving a clean read/write split.

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