Skip to main content
Glama

set_lens_blur_bokeh

Adjust the bokeh shape in lens blur effects to customize background blur aesthetics in Lightroom Classic photo edits.

Instructions

Set the lens blur bokeh shape.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bokehYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The implementation of the `set_lens_blur_bokeh` MCP tool in `server.py`. It registers the tool with the `@mcp.tool()` decorator and calls the underlying `develop.set_lens_blur_bokeh` bridge command.
    @mcp.tool()
    async def set_lens_blur_bokeh(bokeh: str) -> dict[str, Any]:
        """Set the lens blur bokeh shape."""
        if not bokeh:
            raise ValueError("bokeh shape is required")
        return await _call("develop.set_lens_blur_bokeh", {"bokeh": bokeh})
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without disclosing behavioral traits like whether it's a mutation, requires specific photo states, has side effects, or interacts with other settings. It's minimal and lacks critical context for safe invocation.

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?

The description is a single, direct sentence with no wasted words, making it highly concise and front-loaded. It efficiently states the tool's purpose without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has an output schema (which reduces need to describe returns) but no annotations and low parameter coverage, the description is incomplete. It covers the basic purpose but lacks usage, behavioral, and parameter details needed for effective tool selection and invocation in this context.

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

Parameters2/5

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

Schema description coverage is 0%, and the description adds no meaning beyond the schema's parameter name 'bokeh'. It doesn't explain what values are acceptable, format, or effects, failing to compensate for the low coverage and leaving the parameter poorly documented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Set the lens blur bokeh shape' clearly states the action (set) and target (lens blur bokeh shape), but it's vague about what 'bokeh shape' entails and doesn't differentiate from sibling tools like 'toggle_lens_blur_depth_viz' or other lens-related operations. It avoids tautology but lacks specificity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives, such as other lens blur or develop parameter tools in the sibling list. The description implies usage for setting bokeh shape but offers no context, prerequisites, or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/4xiomdev/lightroom-classic-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server