Skip to main content
Glama

obsbot_tail2_gimbal_move

Move the Tail 2 gimbal to an absolute yaw/pitch in degrees via closed-loop jogging; disable AI tracking first, as the tool refuses while tracking is active.

Instructions

Move the Tail 2's gimbal to an absolute yaw/pitch in degrees — the Tail 2's pose-record convention (obsbot_tail2_gimbal_position reports the same axes). There is no move-to-angle endpoint in the API, so this is a closed loop over the speed primitive: jog, read the pose (each read ~2s), correct, up to 5 rounds, tolerance ±1.5°. Slow by design — expect ~5-15s. REFUSES while AI tracking is active (tracking drives the gimbal itself and would fight the loop); obsbot_tail2_ai_track enabled:false first.

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

Input Schema

NameRequiredDescriptionDefault
yawNo
pitchNo
cameraNo

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.4/5.0
Behavior5/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 so unusually well: it explains the closed-loop mechanism (jog, read pose at ~2s per read, correct, up to 5 rounds, ±1.5° tolerance), the expected 5-15s duration, and a hard precondition that causes refusal. These are non-obvious traits the agent could not infer from the schema or from any annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action, then the mechanism, then the cost, then the blocker at the end where a pre-flight check belongs. Sentences are dense with facts (timing, round cap, tolerance, refusal condition) and contain no filler.

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, 3-parameter motion tool, this covers mechanism, latency, accuracy, and preconditions well. The remaining gap is failure semantics: it never says what happens if the loop exhausts 5 rounds without reaching tolerance, or what the call returns (final pose vs. ack), and the camera parameter is unaddressed.

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%, and the description compensates partially: yaw/pitch are absolute angles in degrees, using the same pose-record axes that gimbal_position reports, with ±1.5° accuracy. However, the third parameter (camera) is never mentioned, the ±178 range is left to the schema, and it doesn't say what happens when yaw or pitch is omitted (required count is 0).

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 with units: "Move the Tail 2's gimbal to an absolute yaw/pitch in degrees." It also implicitly separates itself from siblings by naming gimbal_position (which reads the pose) and the speed primitive that this tool loops over, so an agent can tell it apart from obsbot_tail2_gimbal_speed and obsbot_tail2_gimbal_position without opening any 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?

Gives a clear usage context and an explicit exclusion with a remedy: it REFUSES while AI tracking is active, and obsbot_tail2_ai_track enabled:false must be called first. It also discloses cost/latency so the agent can choose it deliberately. What it doesn't say is when to prefer a direct speed jog (obsbot_tail2_gimbal_speed) or obsbot_tail2_recenter over this slow closed loop.

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