Skip to main content
Glama

obsbot_image_exposure_manual

Sets manual exposure for an OBSBOT Tiny 2 webcam on a 0–100 scale (0 darkest, 100 brightest), maps the level to the device's exposure range, and returns the raw value for diagnostics.

Instructions

Set exposure level 0-100 (0 darkest → 100 brightest), mapped onto the device's exposure range. Also returns raw: the device-native exposure value the level mapped to, for diagnostics — level is the number to reason with. Uses the proprietary V3 frame protocol (CAM_SET_EXPOSURE_TINY2, which carries mode and value in one command) because the standard UVC/IAMCameraControl V4L2 path is a stub on the Tiny 2.

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

Input Schema

NameRequiredDescriptionDefault
levelNo
cameraNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.9.6
    • removedInput schema / properties / level / allOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "maximum": 100,
      -    "minimum": 0,
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / level / maximum
      Added value: +100
    • addedInput schema / properties / level / minimum
      Added value: +0
    • addedInput schema / properties / level / type
      Added value: +"number"
  2. First observedv0.6.2

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does add genuine value by explaining that the value is remapped onto a device range, that a device-native `raw` value is returned for diagnostics, and which proprietary protocol (CAM_SET_EXPOSURE_TINY2) is used and why. However, it says nothing about permissions, whether concurrent auto-exposure state is overridden, or failure modes on unsupported devices.

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 core contract (level range and meaning) is front-loaded in the first clause, and the protocol rationale follows as supporting context. The V3/UVC detail is dense but short and explains a real quirk; it could have been trimmed slightly but does not obscure the main instruction.

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?

With no output schema and no annotations, the description still covers the essential behavior: input scale, device remapping, and the returned `raw` diagnostic value, plus why the standard V4L2 path is unusable. The remaining gap is the undocumented `camera` parameter, which is the one thing an agent could still get wrong.

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 for both parameters. It fully explains `level` (0-100, direction, remapping) but leaves the `camera` string parameter completely unspecified — no hint about identifier format, defaulting, or whether it is optional in practice.

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 and resource — 'Set exposure level 0-100' with direction ('0 darkest → 100 brightest') — so the agent knows exactly what changes. It implicitly separates itself from the auto-exposure sibling by being the manual setter, but never names obsbot_image_exposure_auto or obsbot_tail2_exposure as alternatives.

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?

Usage is implied by the word 'manual' and by the numeric level, but there is no explicit when-to-use / when-not-to-use guidance and no routing to obsbot_image_exposure_auto for the automatic case. The agent must infer the manual-vs-auto split from sibling names.

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