Skip to main content
Glama

obsbot_tail2_gesture

Read or set the OBSBOT Tiny 2 webcam's gesture-control switches—locked target, recording and zoom—plus the zoom factor each zoom gesture applies, with write values read back to verify.

Instructions

Read (bare) or set the gesture-control switches and the gesture zoom factor: lockedTarget, recording, zoom (booleans) and zoomFactor (the multiplier one zoom gesture applies, e.g. 2.0). All measured on the wire 2026-10-01. Writes are readback-verified; each field is optional.

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

Input Schema

NameRequiredDescriptionDefault
zoomNo
cameraNo
recordingNo
zoomFactorNo
lockedTargetNo

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose two useful traits: writes are readback-verified and every field is optional (partial update). It does not say what a bare read returns, whether changing switches mid-recording has side effects, or what permissions the device requires, so meaningful gaps remain.

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?

Two compact sentences, front-loaded with the read/write distinction and the field list, with no filler. The provenance clause 'All measured on the wire 2026-10-01' is the weakest sentence, since it conveys protocol-verification timing rather than guidance an agent can act on.

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?

For a five-parameter, no-annotation, no-output-schema tool, the definition covers update semantics and the key fields but leaves the camera selector and the read-path return shape unexplained. An agent knows how to write but must guess which camera it is addressing.

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 do the work, and it explains four of five parameters well — most importantly zoomFactor, whose meaning ('the multiplier one zoom gesture applies, e.g. 2.0') is not derivable from a bare number type. The 'camera' string parameter is entirely undocumented 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?

States a specific verb pair (read or set) and a specific resource (gesture-control switches plus gesture zoom factor), and enumerates the exact fields involved. The 'gesture' qualifier helps separate it from the many other zoom siblings, though it never names obsbot_tail2_zoom or obsbot_tail2_auto_zoom_speed explicitly.

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?

'Read (bare) or set' gives a usable rule for read-versus-write invocation, which is genuinely helpful since the tool is a dual-mode getter/setter. However, there is no guidance on when to use this gesture zoom factor instead of the sibling zoom tools (obsbot_tail2_zoom, obsbot_tail2_hybrid_zoom, obsbot_tail2_auto_zoom_speed), and no prerequisites or exclusions are stated.

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