Skip to main content
Glama

obsbot_tail2_auto_zoom_speed

Set the AI-tracking auto-zoom framing speed (1–10) so tracked subjects stay framed without abrupt zoom changes. Controls the auto-zoom rate separately from manual zoom speed.

Instructions

Set the AUTO zoom speed 1-10 — how fast AI-tracking auto-zoom framing moves (Center's Console slider; distinct from the MANUAL zoom speed on obsbot_tail2_zoom's speed param). Rides UDP 9999 key 0x17. No REST-readable state; no ack — the frame is synthesized and works with Center closed.

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": {
      "speed": "<speed>"
    },
    "name": "obsbot_tail2_auto_zoom_speed"
  }
}

Input Schema

NameRequiredDescriptionDefault
speedYes
cameraNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.9.6
    • 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.2

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations supplied the description carries the full behavioral burden and does so unusually well: it discloses the transport (UDP 9999, key 0x17), that the frame is synthesized rather than requested, that there is no ack, that no REST-readable state exists so the value cannot be read back, and that it works with Center closed. Those are exactly the fire-and-forget, unverifiable-write facts an agent needs before calling it.

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 verb, range, and the key auto-vs-manual distinction, with transport details pushed to the back. Dense and nearly waste-free, though the em-dash-and-parenthetical stacking makes the single sentence heavier to parse than necessary.

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 no-annotation, no-output-schema write tool, the description covers safety profile, transport, ack behavior, and state readability, which is most of what an agent needs. The remaining gap is the undocumented camera parameter, which leaves a caller guessing about multi-device targeting.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 adds real meaning for speed (range 1-10 plus the semantic direction that higher means faster framing movement), but the second parameter, camera, is never mentioned at all and its type/format remains undocumented anywhere. Partial compensation for a 2-param tool where one param is entirely opaque.

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 (Set), a specific resource (AUTO zoom speed), and the valid range 1-10, plus it explains what the value controls: the speed of AI-tracking auto-zoom framing. It explicitly distinguishes itself from the similarly-named sibling obsbot_tail2_zoom speed param (MANUAL zoom), so an agent can tell the two apart without opening either schema.

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

Usage Guidelines4/5

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

The auto-vs-manual framing-speed distinction gives clear routing guidance, and naming obsbot_tail2_zoom's speed param as the MANUAL counterpart is an explicit alternative. It stops short of stating outright 'use this when you want X, use track_speed when Y' or listing prerequisites/exclusions, so it is a strong 4 rather than a 5.

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