Skip to main content
Glama

obsbot_tail2_preset_save

Save the Tail 2 camera's current live pose into preset slot 1–3 after aiming via tracking, recall, or manually. Capture the present framing; saving overwrites any existing slot.

Instructions

Save a Tail 2's CURRENT live pose into a slot (1–3): aim the camera first (via tracking, a recall, or physically), then save. name defaults to P1/P2/P3. NOTE: unlike the Tiny 2, save OVERWRITES an occupied slot (no create-once), and there is no explicit-pose write in this API at all — a slot always captures the camera's CURRENT pose (measured 2026-09-26; TAIL2-PROTOCOL.md §3) — deleting first is unnecessary. Hardware-verified 2026-09-26.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
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

A4.3/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does the important part: it discloses that save OVERWRITES an occupied slot, so the agent knows this is a destructive, non-idempotent-in-spirit write that cannot be undone via this API. It also states the slot always captures the live measured pose, preventing a false 'write arbitrary coordinates' assumption. It stops short of error behavior for an out-of-range slot or what the call returns.

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 action, then the prerequisite, then the semantics that differ from the Tiny 2 — a sensible ordering with almost no filler. The citation tail ('measured 2026-09-26; TAIL2-PROTOCOL.md §3', 'Hardware-verified 2026-09-26') is duplicated and slightly noisy, but it earns credibility for the non-obvious overwrite claim.

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 3-parameter mutation with no annotations and no output schema, the description covers the traits that actually matter: destructiveness, capture semantics, and the aiming precondition. The gaps are the unexplained 'camera' parameter and no hint about failure modes or return value, which keep it below complete.

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, and it only partly does: 'slot (1–3)' restates the schema bounds, while 'name defaults to P1/P2/P3' adds genuine meaning the schema does not carry (default naming behavior). The third parameter, camera, is never mentioned in the description and has no schema description, leaving it 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 ('Save a Tail 2's CURRENT live pose into a slot (1–3)') and immediately scopes it to the Tail 2 rather than the generic sibling obsbot_preset_save. An agent can distinguish it from obsbot_tail2_preset_recall, _rename, and _delete from the first sentence alone.

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?

Gives an explicit prerequisite sequence — 'aim the camera first (via tracking, a recall, or physically), then save' — which names the recall path as the way to reach a prior pose. It also rules out a competing interpretation ('deleting first is unnecessary', 'no explicit-pose write') that would otherwise cause an agent to call preset_delete or a generic preset_update first.

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