Retrieve current Blender render settings, including engine, resolution, sampling, output, and color management, to inspect or verify the active configuration.
当前渲染设置（引擎、分辨率、采样、输出、色彩管理）。
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Although no annotations are present, the description explicitly indicates a read-only operation by saying 'current' settings. This discloses that it retrieves state without modification, which is sufficient given the simple getter nature.
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, concise sentence without unnecessary details or redundancy. It front-loads the main purpose and lists relevant components efficiently.
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?
Given no parameters and no output schema, the description fully captures the tool's scope by listing the settings it retrieves. No additional information is needed for a user to understand its function.
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 tool has zero parameters, so there is no parameter semantics to describe. The baseline for no parameters is 4, and the description adequately covers the tool's purpose.
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 'current render settings' and enumerates specific aspects (engine, resolution, samples, output, color management), making it a precise getter. This distinguishes it from sibling tools like set_render_settings.
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?
The description implies usage as a getter for current render settings, but does not explicitly state when to prefer this over alternatives such as set_render_settings or render_image. The context is clear but not explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.