Skip to main content
Glama

obsbot_tail2_track_custom

Configure custom AI tracking speed for an OBSBOT camera: enable tracking, set pan and tilt speeds from 1–10, toggle per-axis auto modes, and read current tracking settings.

Instructions

Configure CUSTOM tracking speed (Center's customized track speed): enable it, set the per-axis Pan/Tilt speeds 1-10, and toggle the per-axis Auto buttons. Bare call reads current state from the status push (tracking_settings, locks included read-only). Writes ride UDP 9999 keys 04/07/0a/06/09 (pan/tilt travel as float32 slider/10 on the wire; keys 06/09 are the Auto buttons — hardware-verified against horizontal_auto/vertical_auto). The AXIS LOCKS have no known write path (not UDP, REST guesses 404) — shown read-only. Verified by tracking_settings readback.

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

Input Schema

NameRequiredDescriptionDefault
panNo
tiltNo
cameraNo
enabledNo
panAutoNo
tiltAutoNo

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does well: it discloses that writes go over UDP port 9999 using keys 04/07/0a/06/09, that pan/tilt travel is float32 slider/10 on the wire, that axis locks have no write path and are shown read-only, and that changes are confirmed via tracking_settings readback. The only notable gap is that it does not describe failure behavior if the device is unreachable.

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?

The write/read behavior and operational parameters are front-loaded, and the protocol detail is dense but each clause carries real information an agent could not get from the schema. It leans jargon-heavy ('keys 04/07/0a/06/09') in a way that could be tightened, but nothing is redundant.

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 six-parameter mutation tool with no annotations and no output schema, the definition covers read mode, write transport, units, hardware verification, and a documented read-only limitation. Only the undocumented `camera` parameter and error handling keep it from being 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 description coverage is 0%, so the description must compensate, and it largely does: it explains the 1-10 range for pan/tilt, that panAuto/tiltAuto map to keys 06/09 (hardware-verified against horizontal_auto/vertical_auto), and that `enabled` activates the customized profile. The `camera` parameter is never mentioned anywhere, which is the main omission.

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 names a specific verb and resource: configure CUSTOM tracking speed, set per-axis Pan/Tilt speeds 1-10, and toggle per-axis Auto buttons. It implicitly distinguishes itself from the sibling obsbot_tail2_track_speed by emphasizing 'CUSTOM' / Center's `customized` speed profile, but never names that sibling outright, so the differentiation is inferential rather than explicit.

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 states that a bare call reads current state and that supplying values performs writes, which is useful usage context. However, it never says when to prefer this over obsbot_tail2_track_speed or the other gimbal-speed siblings, and no prerequisites or exclusions are given.

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