Skip to main content
Glama

obsbot_tail2_iso_range

Read or set the auto-ISO range bounds (100–6400) for the OBSBOT Tiny 2 webcam. Pass min and/or max to adjust the double-ended slider; omitted values keep the current setting.

Instructions

Read or set the auto-ISO range (the double-ended slider: both bounds, 100-6400 in doubling stops). Pass min and/or max; both default to the current value when omitted. 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_iso_range"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNo
minNo
cameraNo

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it discloses the 100-6400 range, that the range moves in doubling stops, partial-update semantics (omitted bound keeps current value), and that writes are readback-verified. It does not say what happens on a non-ladder value or whether the setting persists across power cycles.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact sentences, zero filler, front-loaded with the action and resource before the operational detail. 'Readback-verified write' is a dense, high-value trailing clause 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 no-annotation, no-output-schema, three-parameter tool, the description covers the read/write duality, the valid value ladder, and default behavior, which is enough to call it correctly. The unaddressed camera selector and the absence of any note on what a read returns keep it from being complete.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must supply parameter meaning, and it does for min/max: bounds of one slider, doubling stops, and default-to-current behavior when omitted. The third parameter, camera, is left entirely unexplained, which is the main remaining gap.

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?

Specific verb pair plus a precise resource: 'Read or set the auto-ISO range,' with a parenthetical clarifying it is the double-ended slider with both bounds. An agent can easily distinguish this from exposure/wb/manual-ISO siblings. It stops short of naming those siblings explicitly, so it falls just short of a 5.

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?

The mechanics of use are clear (pass min and/or max; omitted bounds keep current values), which implicitly defines read mode as 'omit both.' However, there is no explicit statement of when to prefer this over obsbot_tail2_exposure or obsbot_image_exposure_manual, nor any stated precondition such as the camera needing to be in auto-ISO mode.

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