Skip to main content
Glama

obsbot_tail2_zoom

Set an absolute 1.0–12.0 zoom ratio on an OBSBOT Tail 2 camera with a required speed value, then poll the readback to check whether the mechanical zoom settled.

Instructions

Set absolute zoom ratio on a Tail 2 (1.0–12.0 — twelve x, six times the Tiny 2's range; scale is the camera's own ratio, not a magnification multiple). speed 1–10 is REQUIRED by the firmware and defaults to 5. Zoom ramps mechanically; the tool polls the readback and returns settled:false if it hadn't arrived within ~5s — the command was still sent. Hardware-verified 2026-09-26.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ratio": "<ratio>"
    },
    "name": "obsbot_tail2_zoom"
  }
}

Input Schema

NameRequiredDescriptionDefault
ratioYes
speedNo
cameraNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.9.6
    • removedInput schema / properties / ratio / allOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "maximum": 12,
      -    "minimum": 1,
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / ratio / maximum
      Added value: +12
    • addedInput schema / properties / ratio / minimum
      Added value: +1
    • addedInput schema / properties / ratio / type
      Added value: +"number"
    • removedInput schema / properties / speed / allOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "maximum": 10,
      -    "minimum": 1,
      -    "type": "integer"
      -  }
      -]
    • addedInput schema / properties / speed / maximum
      Added value: +10
    • addedInput schema / properties / speed / minimum
      Added value: +1
    • addedInput schema / properties / speed / type
      Added value: +"integer"
  2. Addedv0.9.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden, and it does more than most: mechanical ramp, internal polling of the readback, ~5s settle window, and a settled:false result that still means the command was sent. That last point is genuinely valuable for a mutating call. However, it never states permission/connection requirements, what happens to concurrent zoom commands, or whether the camera must be awake — gaps that matter with zero annotation coverage.

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 action and range, then behavior, then provenance — a sensible ordering with no filler sentences. The parenthetical asides ("twelve x, six times the Tiny 2's range", "the command was still sent") are dense but each carries information; minor tightening is possible.

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 3-parameter hardware-mutation tool with no annotations and no output schema, the description supplies the settle/timeout semantics and the meaning of the returned flag, which is exactly what an agent needs to interpret results. Only the unexplained camera parameter and unstated device-state prerequisites keep it from being fully complete.

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, and it does for two of three parameters: ratio is given its range and unit semantics, and speed is given its range plus the non-obvious fact that firmware requires it and 5 is the default. The third parameter, camera, is never mentioned, leaving its role (device selection?) entirely to guesswork.

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+resource ("Set absolute zoom ratio on a Tail 2") and disambiguates the unit of the ratio ("the camera's own ratio, not a magnification multiple"). It does not name the sibling zoom tools (obsbot_tail2_hybrid_zoom, obsbot_tail2_zoom_type, obsbot_tail2_auto_zoom_speed) it must be chosen over, so differentiation is by concept rather than explicit routing.

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?

The phrase "absolute zoom ratio" and the Tiny 2 comparison imply this is the direct/manual zoom setter, but there is no explicit statement of when to use it versus hybrid_zoom, zoom_type, or auto_zoom_speed. No prerequisites, no when-not conditions, no alternative named.

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