protein-blender-mcp

set_background

Set the camera background to a color name, hex value, or transparent for compositing; lighting stays separate so dark backgrounds still illuminate molecules, with adjustable lighting strength.

Instructions

Set the background color the camera sees (name or hex), or make it transparent for figures placed on another background. Lighting is kept separate, so dark backgrounds still light the molecule; raise lighting_strength (e.g. 1.5) for a brighter scene.

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": "set_background"
  }
}

Input Schema

Name	Required	Default
`color`	No	white
`transparent`	No
`lighting_strength`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 7, 2026

TDQS

A3.6/5.0

Behavior3/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 add real behavioral context: lighting is independent of background, so dark backgrounds still light the molecule, and lighting_strength is the remedy. It omits other relevant traits such as whether the setting persists across renders, whether it interacts with render settings, or whether it is reversible.

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-loading the core action and following with compositing and lighting caveats; nothing is padding. Slightly informal phrasing and line breaks, but no wasted content.

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 simple, no-output three-parameter scene tool with no annotations, the description covers every parameter and the one non-obvious behavior (lighting independence). The main gap is its relationship to related render settings tools, which goes unmentioned.

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 compensate, and it does for all three parameters: color accepts a name or hex, transparent is for compositing on another background, and lighting_strength has a concrete suggested value (e.g. 1.5). It stops short of stating defaults or accepted color-name vocabulary, but the added meaning is substantial.

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?

Uses a specific verb and resource: 'Set the background color the camera sees', and clarifies the scope (camera-visible background, not molecule lighting). An agent can tell what it does, though the description never contrasts it with set_render_settings, which plausibly also touches background/visual output.

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?

Implied usage guidance is present: use transparent for figures composited onto another background, and raise lighting_strength for bright scenes. However there is no explicit statement of when to prefer this tool over siblings like set_render_settings or set_render_settings-adjacent tools, and no when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server