Skip to main content
Glama

lightroom_status

Check the operational status, command availability, and connection state of the Lightroom Classic MCP server to verify functionality before executing photo editing tasks.

Instructions

Get plugin status, command count, and socket state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool definition and handler for lightroom_status, which calls the system.status method on the Lightroom plugin via an internal _call function.
    @mcp.tool()
    async def lightroom_status() -> dict[str, Any]:
        """Get plugin status, command count, and socket state."""
        return await _call("system.status")
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 mentions what data is retrieved but lacks details on permissions, rate limits, error handling, or the format of returned data. While an output schema exists, the description doesn't add behavioral context beyond the basic retrieval action.

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 directly states the tool's purpose with no wasted words. It is front-loaded and clear, making it easy for an agent to parse and understand 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 0 parameters and an output schema exists, the description adequately covers the basic purpose. However, with no annotations and sibling tools that might overlap, it lacks context on when to use it and behavioral details, making it only minimally complete for a simple status-checking tool.

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?

The tool has 0 parameters with 100% schema description coverage, so no parameter information is needed in the description. The description appropriately focuses on the tool's purpose without redundant parameter details, earning a high score as it adds value by explaining what is retrieved without unnecessary repetition.

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 tool's purpose with specific verbs ('Get') and resources ('plugin status, command count, and socket state'), making it easy to understand what information it retrieves. However, it doesn't explicitly differentiate from sibling tools like 'lightroom_ping' or 'lightroom_list_commands', which might offer overlapping functionality, preventing a perfect score.

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. The description doesn't mention prerequisites, context for usage, or comparisons to sibling tools like 'lightroom_ping' (which might check connectivity) or 'lightroom_list_commands' (which might list available commands), leaving the agent without clear usage instructions.

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