Skip to main content
Glama

select_mask_tool

Choose a masking tool in Lightroom Classic to apply localized adjustments: brush, graduated filter, radial filter, or range mask.

Instructions

Select a mask tool: brush, graduated-filter, radial-filter, or range-mask.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toolYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The `select_mask_tool` function is defined as an MCP tool, which calls the bridge command 'masks.select_tool'.
    @mcp.tool()
    async def select_mask_tool(tool: str) -> dict[str, Any]:
        """Select a mask tool: brush, graduated-filter, radial-filter, or range-mask."""
        if not tool:
            raise ValueError("tool is required")
        return await _call("masks.select_tool", {"tool": tool})
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a selection action but doesn't explain the effects (e.g., whether this changes the active tool in Lightroom, if it's reversible, or what permissions are needed). This leaves significant gaps in understanding the tool's behavior.

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 description is a single, efficient sentence that directly states the tool's function and options. It's front-loaded with the main action and avoids unnecessary details, though it could be slightly more structured by clarifying the context.

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's low complexity (1 parameter) and the presence of an output schema (which likely handles return values), the description is minimally adequate. However, with no annotations and incomplete parameter semantics, it lacks depth for effective use, especially compared to sibling tools in a Lightroom 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%, so the description must compensate. It lists possible values for the 'tool' parameter (brush, graduated-filter, radial-filter, range-mask), adding meaning beyond the schema's generic string type. However, it doesn't explain what these tools do or how to choose between them, providing only partial semantic context.

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 states the action ('Select a mask tool') and lists the available options, which clarifies the purpose. However, it doesn't specify what 'mask tool' means in this context or differentiate from sibling tools like 'select_mask' or 'create_ai_mask', making it somewhat vague.

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 like 'select_mask' or 'create_ai_mask'. The description merely lists options without context for selection, offering no usage instructions or prerequisites.

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