Skip to main content
Glama

obsbot_tail2_roll_bias

Set a Tail 2 camera's roll trim angle in degrees to correct the horizon or apply a deliberate tilt, clamped to ±90. Adjusts the actual image, unlike inert Tiny 2 roll slots.

Instructions

Set a Tail 2's roll trim angle in degrees (horizon correction / deliberate tilt), clamped to ±90. Unlike the Tiny 2 (whose roll slot is inert), this moves the image. Verified write+readback on hardware 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": {
      "angle": "<angle>"
    },
    "name": "obsbot_tail2_roll_bias"
  }
}

Input Schema

NameRequiredDescriptionDefault
angleYes
cameraNo

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description must carry the full load; it does disclose that this is a write operation, that it alters the image, and that it was verified with write+readback on hardware on a specific date. It omits persistence across power cycles, behavior on out-of-range input (silent clamp vs error), and whether the change is relative or absolute.

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?

Two tight sentences, front-loaded with purpose and range, then the sibling contrast and hardware verification. The dated hardware-verification clause is somewhat expendable but does convey reliability evidence 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 tool with no annotations and no output schema, the description covers purpose, range, unit, and device-model applicability, which is most of what an agent needs. The unexplained 'camera' parameter and missing return/readback format keep it from being fully 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 coverage is 0%, so the schema alone gives no meaning to the parameters. The description supplies the critical unit (degrees) and the ±90 clamp for 'angle', which the bare number in the schema lacked, but the optional 'camera' parameter is never explained (device selector? index? name?), leaving half the surface undocumented.

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?

Description states a specific verb and resource ('Set a Tail 2's roll trim angle'), gives the unit (degrees), the range, and the two intents (horizon correction vs deliberate tilt). It also explicitly contrasts with the Tiny 2 whose roll slot is inert, so an agent can distinguish intent from sibling gimbal/recenter tools.

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?

Implied usage is clear (correct a tilted horizon or intentionally tilt the image), and the Tiny 2 contrast tells the agent when this tool has an effect vs when it does not. It stops short of naming an alternative for resetting roll, e.g. obsbot_tail2_recenter or obsbot_tail2_gimbal_move, or stating prerequisites such as camera selection.

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