Set the camera's white balance to a chosen color temperature in Kelvin. Ensures accurate colors under varied lighting by clamping to the device's supported range.
Set white balance to a colour temperature in Kelvin (clamped to the device's supported range).
| Name | Required | Description | Default |
|---|---|---|---|
| camera | No | ||
| temperature | No |
Changes observed during successful MCP inspections.
v0.7.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses a useful behavioral trait: the temperature is clamped to the device's supported range, which is beyond what the schema shows. However, with no annotations provided, the description still does not address prerequisites, failure behavior, or whether this affects the current white-balance mode.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single efficient sentence with no filler. It front-loads the core operation and includes the most important behavioral caveat about clamping.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple two-parameter setter, the description conveys the main operation and the temperature constraint well. But without annotations or an output schema, and with the 'camera' parameter undocumented, the description is only minimally complete for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description adds meaning to the 'temperature' parameter by specifying Kelvin units and clamping, improving on the bare schema. However, schema coverage is 0% and the 'camera' parameter is not explained at all, leaving a gap for agents that need to know what camera identifiers are accepted.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action: setting white balance to a Kelvin color temperature, which is specific and tied to the manual white-balance functionality. It does not explicitly differentiate from obsbot_image_wb_auto, but the Kelvin mention makes the manual mode intent fairly clear.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus the sibling obsbot_image_wb_auto or other image adjustment tools. The description does not mention alternatives or provide context such as 'use this when a fixed color temperature is needed.'
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.