Skip to main content
Glama

invert_mask

Reverse the selection of a mask in Lightroom Classic to edit different areas of a photo. Specify a mask ID or invert the active mask.

Instructions

Invert the active mask (or a specific mask by ID).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mask_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler implementation for the 'invert_mask' tool, which uses the '@mcp.tool()' decorator and calls 'masks.toggle_invert' via an internal '_call' method.
    @mcp.tool()
    async def invert_mask(mask_id: int | None = None) -> dict[str, Any]:
        """Invert the active mask (or a specific mask by ID)."""
        payload: dict[str, Any] = {}
        if mask_id is not None:
            payload["mask_id"] = mask_id
        return await _call("masks.toggle_invert", payload)
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('invert') but doesn't explain what 'invert' means in this context (e.g., does it toggle visibility, reverse selection, or change properties?), whether it requires specific permissions, or what the output might be. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the key information ('Invert the active mask') and adds optional details concisely. There is no wasted text, making it easy to parse quickly.

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 one parameter with low schema coverage and an output schema exists (which reduces the need to describe return values), the description is minimally adequate. However, for a tool that performs an operation ('invert') with potential side effects, more context on behavior and usage would improve completeness, especially since no annotations are provided.

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

Parameters3/5

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

The input schema has one parameter ('mask_id') with 0% description coverage, and the description adds some meaning by explaining it as 'a specific mask by ID' and mentioning the default case ('the active mask'). However, it doesn't provide details on ID format, what 'active mask' means, or how the tool behaves with null vs. integer values, so it partially compensates but not fully.

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?

The description clearly states the action ('invert') and the target ('the active mask or a specific mask by ID'), making the purpose understandable. However, it doesn't explicitly differentiate this tool from sibling tools like 'select_mask' or 'toggle_mask_overlay', which might involve mask operations but serve different purposes.

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?

The description provides minimal guidance by mentioning 'the active mask (or a specific mask by ID)', implying it can be used in two contexts, but it doesn't specify when to use this tool versus alternatives like 'toggle_mask_overlay' or other mask-related tools in the sibling list. No explicit when/when-not or alternative recommendations are provided.

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