Skip to main content
Glama

obsbot_tail2_gimbal_speed

Jog the OBSBOT Tail 2 gimbal by setting per-axis yaw, pitch, and roll speed for a timed interval, then automatically stop the move. Disable AI tracking first to prevent it from fighting the command.

Instructions

Jog the Tail 2's gimbal: per-axis SPEED (sign = direction, magnitude = speed, ±150 of the firmware's ±178 range) with an automatic stop after durationMs (default 500, max 5000). This is the joystick primitive (POST ptz/gimbalcontrol) — there is no absolute move endpoint, so the camera moves continuously until stopped; this tool always stops it. Measured: command 20 ≈ 7.9°/s, and a POSITIVE yaw command DECREASES the recorded yaw (obsbot_tail2_gimbal_position's convention). Disable AI tracking first or it will fight the move.

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

Input Schema

NameRequiredDescriptionDefault
yawNo
rollNo
pitchNo
cameraNo
durationMsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changedv0.9.6
    • removedInput schema / properties / durationMs / allOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "maximum": 5000,
      -    "minimum": 100,
      -    "type": "integer"
      -  }
      -]
    • addedInput schema / properties / durationMs / maximum
      Added value: +5000
    • addedInput schema / properties / durationMs / minimum
      Added value: +100
    • addedInput schema / properties / durationMs / type
      Added value: +"integer"
    • removedInput schema / properties / pitch / allOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "maximum": 150,
      -    "minimum": -150,
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / pitch / maximum
      Added value: +150
    • addedInput schema / properties / pitch / minimum
      Added value: +-150
    • addedInput schema / properties / pitch / type
      Added value: +"number"
    • removedInput schema / properties / roll / allOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "maximum": 150,
      -    "minimum": -150,
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / roll / maximum
      Added value: +150
    • addedInput schema / properties / roll / minimum
      Added value: +-150
    • addedInput schema / properties / roll / type
      Added value: +"number"
    • removedInput schema / properties / yaw / allOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "maximum": 150,
      -    "minimum": -150,
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / yaw / maximum
      Added value: +150
    • addedInput schema / properties / yaw / minimum
      Added value: +-150
    • addedInput schema / properties / yaw / type
      Added value: +"number"
  2. Addedv0.9.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does most of it: it discloses the underlying POST ptz/gimbalcontrol primitive, continuous-until-stopped motion, that the tool always issues a stop, the duration default (500ms) and cap (5000ms), and the measured 20 ≈ 7.9°/s scaling. It omits auth/permission needs, error behavior, and what the response contains, which keeps it below a 5.

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 core action and free of filler; every clause (units, stop behavior, sign inversion, AI-tracking caveat) carries real information. The dense parenthetical packing makes it marginally harder to scan but nothing is expendable.

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 and no annotations, yet the description covers the motion model, timing, scaling, coordinate convention, and the main conflict (AI tracking). It is nearly complete for a 5-parameter motion tool; only the camera parameter and return/response behavior are unaddressed.

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 does for most parameters: it explains that magnitude is speed, that sign is direction, why the schema clamps at ±150 against the firmware's ±178, and the durationMs default/max. The pitch/roll sign behavior and especially the 'camera' string parameter are never explained, leaving one parameter fully 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 and resource ('Jog the Tail 2's gimbal') plus the exact control semantic (per-axis SPEED, sign = direction). It also distinguishes itself from an absolute-move alternative by noting there is no absolute move endpoint, so the agent knows this is the continuous joystick primitive.

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?

Explicitly tells the agent when to use it (joystick primitive for continuous motion) and gives a concrete prerequisite: 'Disable AI tracking first or it will fight the move.' It also rules out looking for an absolute-move endpoint and names obsbot_tail2_gimbal_position as the reference for the coordinate convention.

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