Skip to main content
Glama
Sign In
Lightroom Classic MCP

Lightroom Classic MCP

by 4xiomdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

toggle_mask_overlay

Control mask overlay visibility in Lightroom Classic to manage editing adjustments and refine photo selections during professional workflows.

Instructions

Toggle the mask overlay visualization on/off.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/lightroom_mcp_custom/server.py:694-696 (handler)
    The handler function `toggle_mask_overlay` which calls the underlying `masks.toggle_overlay` command.
    async def toggle_mask_overlay() -> dict[str, Any]:
    """Toggle the mask overlay visualization on/off."""
    return await _call("masks.toggle_overlay")
  • src/lightroom_mcp_custom/server.py:693-696 (registration)
    The `@mcp.tool()` decorator used to register the `toggle_mask_overlay` function as an MCP tool.
    @mcp.tool()
async def toggle_mask_overlay() -> dict[str, Any]:
    """Toggle the mask overlay visualization on/off."""
    return await _call("masks.toggle_overlay")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the toggle action but doesn't explain what the mask overlay is, whether it's persistent across sessions, what visual effect it has, or any side effects. For a visualization toggle with zero annotation coverage, this is inadequate.

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 with zero wasted words. It's perfectly front-loaded and communicates the core functionality immediately.

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 no parameters, an output schema exists, and it's a simple toggle operation, the description is minimally complete. However, it lacks context about what the mask overlay actually is or when it would be useful, which would help an agent understand its purpose better.

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?

With 0 parameters and 100% schema description coverage, the baseline is 4. The description doesn't need to explain parameters since there are none, and it correctly matches the empty input schema.

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 ('toggle') and the target ('mask overlay visualization'), making the purpose immediately understandable. It doesn't distinguish from sibling tools, but since no other tools mention mask overlays, this is sufficient for clarity.

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 no guidance on when to use this tool versus alternatives, prerequisites, or contextual constraints. It's a bare statement of functionality without usage context.

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

Deploy Server

Other Tools