Skip to main content
Glama

obsbot_tail2_focus

Read or set the Tail 2 camera's focus mode (afc/afs/mf) and manual focus position, rejecting position changes in auto modes to prevent camera errors.

Instructions

Read (bare call) or set the Tail 2's focus: mode afc|afs|mf, and position (0-100, the focus motor) which is only valid in mf — the camera errors on it in afc/afs and this tool refuses rather than trigger that. Bare call reports the mode, and the position when in mf.

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

Input Schema

NameRequiredDescriptionDefault
modeNo
cameraNo
positionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.9.6
    • removedInput schema / properties / position / allOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "maximum": 100,
      -    "minimum": 0,
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / position / maximum
      Added value: +100
    • addedInput schema / properties / position / minimum
      Added value: +0
    • addedInput schema / properties / position / type
      Added value: +"number"
  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. It usefully discloses that the tool pre-validates and refuses invalid mode/position combinations instead of forwarding a camera error, and it describes what a bare call returns. It does not say whether setting position implicitly requires mode=mf in the same call, nor whether changes persist across sessions.

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 dense sentences that front-load the read/set duality and then the constraint. Every clause carries information; the phrasing 'refuses rather than trigger that' is slightly awkward but not wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter tool with no annotations and no output schema, the description covers the set/read behavior and return values of a bare call adequately. The undocumented camera parameter and unexplained afc/afs distinction leave real gaps for an agent deciding how to address a specific device.

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. It does well for two params: position is defined as the focus motor on 0-100 with the mf-only constraint, and mode's enum is enumerated. However, the meanings of afc versus afs are never explained, and the third parameter (camera) is not mentioned at all.

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 pair (read via bare call / set) and a specific resource (Tail 2 focus mode and motor position), with the enum values inline. It does not distinguish itself from the nearby focus-related siblings such as obsbot_tail2_focus_point or obsbot_focus_auto, so an agent must infer the boundary.

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 explicit conditional usage: bare call to read, parameters present to set, and position only when mode is mf. It also declares a when-not condition (afc/afs with position). What is missing is any comparison to alternative focus tools in the sibling set.

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