Skip to main content
Glama

obsbot_tail2_preset_speed

Read or set the gimbal preset recall speed from 1 to 5, with readback-verified writes to confirm the OBSBOT Tiny 2 setting.

Instructions

Read or set the preset switching speed (1-5, Center's Console page). How fast recalls drive the gimbal. Readback-verified write.

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

Input Schema

NameRequiredDescriptionDefault
speedNo
cameraNo

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It does add genuine value by disclosing that the write is 'readback-verified' and by defining the effect as how fast preset recalls drive the gimbal, but it omits persistence across power cycles, whether a camera must be connected, and failure behavior.

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?

Three short sentences, front-loaded with the read/write duality and the range, with no filler. It is efficient, though the parenthetical '(1-5, Center's Console page)' is slightly compressed and the UI-page reference is of unclear value to an agent.

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?

With no output schema and no annotations, the description should cover more: it explains the read/write duality and readback verification but leaves the camera parameter, the default target camera, and the shape of a read response unspecified. Adequate for a two-parameter tool, but not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 partially does for 'speed' by restating the 1-5 range and what the value controls, but 'camera' is completely undocumented in both schema and description, leaving an agent to guess whether it is a device selector, an index, or optional.

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?

The description gives a specific verb pair plus resource: 'Read or set the preset switching speed', and adds a clarifying gloss ('How fast recalls drive the gimbal') that separates it from gimbal_speed, track_speed, and auto_zoom_speed. It is clear what the tool operates on, though it never explicitly names the sibling speeds it is distinct from.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Read or set' implies the two modes, and the zero required parameters hints that omitting speed performs a read, but this is left to inference rather than stated. There is no guidance on when to prefer this over obsbot_tail2_gimbal_speed or obsbot_tail2_track_speed, nor any prerequisite or ordering advice.

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