Skip to main content
Glama

obsbot_tail2_preset_recall

Recall a saved Tail 2 preset slot (1–3) to drive the gimbal and zoom to a stored pose; disable AI tracking first to prevent it from fighting the move.

Instructions

Recall a Tail 2 preset slot (1–3): drives the gimbal and zoom to the saved pose. Refuses an empty slot. Arrival is verified through the only live observable — the zoom ratio from the status push — so gimbal axes are open-loop (the Tail 2 reports no live pose). Disable AI tracking first or it will fight the move. Hardware-verified 2026-09-26 (zoom 1.5 → saved 3.0 observed).

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": {
      "slot": "<slot>"
    },
    "name": "obsbot_tail2_preset_recall"
  }
}

Input Schema

NameRequiredDescriptionDefault
slotYes
cameraNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.9.6
    • removedInput schema / properties / slot / allOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "maximum": 3,
      -    "minimum": 1,
      -    "type": "integer"
      -  }
      -]
    • addedInput schema / properties / slot / maximum
      Added value: +3
    • addedInput schema / properties / slot / minimum
      Added value: +1
    • addedInput schema / properties / slot / 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?

With no annotations, the description carries the full burden and does well on failure modes (empty slot refusal) and side effects (AI tracking conflict). It also discloses a key limitation: arrival is verified only via zoom ratio, so gimbal axes are open-loop because the device reports no live pose. However, it omits permission/auth needs, whether the motion is blocking or async, and any rate or timing behavior an agent would need for sequencing.

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?

Four tight sentences, front-loaded with the action and range, then the failure mode, then the verification caveat and the tracking precondition. The hardware-verification parenthetical is somewhat tangential but does substantiate the open-loop claim rather than padding.

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 two-parameter mutation with no annotations and no output schema, the description covers the important behavioral surface: what moves, what fails, what must be disabled, and how success is observed. The remaining gap is the undocumented 'camera' parameter and the absence of any statement about blocking versus non-blocking motion.

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 coverage is 0%, so the description must compensate, and it only partially does: the slot parameter's 1–3 range is restated (already in the schema as minimum/maximum) plus the useful 'refuses an empty slot' failure note. The second parameter, 'camera', is never mentioned at all, leaving a required selection opaque to the agent.

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?

States a specific verb and resource: recall a Tail 2 preset slot (1–3), which drives gimbal and zoom to the saved pose. This clearly distinguishes it from siblings like obsbot_tail2_preset_save or obsbot_tail2_preset_delete, though it never contrasts with the generic obsbot_preset_recall sibling that appears in the same list.

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 concrete precondition — 'Disable AI tracking first or it will fight the move' — and a constraint, 'Refuses an empty slot', which tells the agent when the call will fail. It stops short of naming an alternative tool or saying when to prefer obsbot_preset_recall over this Tail 2 variant.

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