Skip to main content
Glama

get_develop_param_range

Retrieve the adjustable slider range for any development parameter in Lightroom Classic to ensure edits stay within valid limits.

Instructions

Get slider range for a develop parameter (when Lightroom can report it).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parameterYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the `get_develop_param_range` tool.
    async def get_develop_param_range(parameter: str) -> dict[str, Any]:
        """Get slider range for a develop parameter (when Lightroom can report it)."""
        if not parameter:
            raise ValueError("parameter is required")
        return await _call("develop.get_param_range", {"parameter": parameter})
  • MCP tool registration for `get_develop_param_range`.
    @mcp.tool()
Behavior2/5

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

No annotations are provided, so the description carries full burden. It hints at conditional behavior ('when Lightroom can report it'), suggesting it may fail or return limited data, but doesn't disclose error handling, rate limits, authentication needs, or what 'slider range' entails. This leaves significant gaps for a tool that likely interacts with external software.

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 waste. It's front-loaded with the core purpose and includes a brief qualifier, making it appropriately sized and easy to parse.

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 one parameter with 0% schema coverage and an output schema exists (so return values needn't be explained), the description is incomplete. It lacks details on parameter semantics and behavioral context, but the presence of an output schema and low complexity keeps it from being severely inadequate. It's minimal but not entirely useless.

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 mentions 'parameter' but doesn't explain what values are valid (e.g., from 'list_develop_parameters'), format, or examples. The description adds minimal meaning beyond the schema's basic parameter name, failing to address the coverage gap adequately.

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 ('Get slider range') and resource ('for a develop parameter'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'list_develop_param_ranges' or 'list_develop_parameters', which appear related, so it lacks sibling distinction.

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 with the parenthetical '(when Lightroom can report it)', implying usage depends on Lightroom's capability, but it doesn't specify when to use this tool versus alternatives like 'list_develop_param_ranges' or prerequisites. No explicit when/when-not or alternative tools are mentioned.

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