Skip to main content
Glama

obsbot_tail2_focus_point

Move the focus window to normalized x/y coordinates and start point focus for tap-to-focus control in AFC/AFS modes. A bare call reads the current window.

Instructions

Tap-to-focus: move the focus window to a normalized frame coordinate (x/y 0.01-0.99, top-left ~0,0) AND start a point focus there. Effective in afc/afs focus modes only — in mf the motor position is the tool (obsbot_tail2_focus). Bare call reads the current window. Divide a snapshot pixel by frameWidth/frameHeight and pass it straight in.

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

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
cameraNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.9.6
    • removedInput schema / properties / x / allOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "maximum": 0.99,
      -    "minimum": 0.01,
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / x / maximum
      Added value: +0.99
    • addedInput schema / properties / x / minimum
      Added value: +0.01
    • addedInput schema / properties / x / type
      Added value: +"number"
    • removedInput schema / properties / y / allOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "maximum": 0.99,
      -    "minimum": 0.01,
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / y / maximum
      Added value: +0.99
    • addedInput schema / properties / y / minimum
      Added value: +0.01
    • addedInput schema / properties / y / type
      Added value: +"number"
  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 well: it discloses the dual side effect (reposition the window AND start point focus), the read-vs-write branch of a bare call, and the camera focus-mode dependency. It does not cover failure behavior (e.g., what happens in mf mode, whether it errors or no-ops) or the shape of the response after a set, which keeps it below a 5.

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?

The key identification (tap-to-focus) is front-loaded, and each sentence carries distinct information: capability, mode constraint, bare-call behavior, coordinate conversion. It is dense but slightly run-on, cramming the mode caveat and the pixel-conversion tip into one line.

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 tool with no output schema and no annotations, this is nearly complete: coordinate space, mode prerequisites, bare-call read behavior, and a practical pixel-to-normalized conversion path are all present. The remaining gap is the undocumented camera parameter and no indication of what a successful set returns.

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 add real meaning for x/y: the top-left origin convention and the recipe "divide a snapshot pixel by frameWidth/frameHeight and pass it straight in." However, the third parameter, camera, is never mentioned, and the numeric bounds are simply repeated from the schema rather than extended.

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?

"Tap-to-focus: move the focus window to a normalized frame coordinate ... AND start a point focus there" names a specific verb pair and resource, and explicitly distinguishes itself from the sibling obsbot_tail2_focus (motor position in mf mode). An agent can pick between the AF point-focus tool and the manual-focus tool without opening either schema.

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?

It states the precondition for effectiveness (afc/afs focus modes only) and the exclusion condition with a named alternative ("in mf the motor position is the tool (obsbot_tail2_focus)"). It also covers the degenerate call case: "Bare call reads the current window," which tells the agent what happens when it omits coordinates.

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