Skip to main content
Glama

list_develop_param_ranges

Retrieve numeric value ranges for Lightroom Classic develop parameters to ensure accurate editing adjustments and prevent invalid settings.

Instructions

Get numeric ranges for known develop parameters (where available).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parametersNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The 'list_develop_param_ranges' tool handler, which fetches ranges for Lightroom develop parameters.
    async def list_develop_param_ranges(parameters: list[str] | None = None) -> dict[str, Any]:
        """Get numeric ranges for known develop parameters (where available)."""
        payload: dict[str, Any] = {}
        if parameters:
            payload["parameters"] = [str(p) for p in parameters if str(p)]
        return await _call("develop.list_param_ranges", payload)
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 states it retrieves ranges but doesn't disclose behavioral traits like whether it's read-only, what 'where available' entails (e.g., partial data), error handling, or output format. This leaves significant gaps for a tool with potential complexity.

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 no wasted words. It's front-loaded with the core action and resource, 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 no annotations, 0% schema coverage, but an output schema exists, the description is moderately complete. It covers the basic purpose but lacks details on behavior, parameters, and usage context, which are needed for full understanding despite the output schema.

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?

Schema description coverage is 0%, so the description must compensate. It implies the tool can fetch ranges for parameters, but doesn't explain the 'parameters' input (e.g., what it accepts, default behavior). This adds minimal semantics beyond the schema, meeting the baseline for low coverage.

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') and the resource ('numeric ranges for known develop parameters'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'list_develop_parameters' or 'get_develop_param_range', which appear related, so it misses full 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 no guidance on when to use this tool versus alternatives, such as 'list_develop_parameters' or 'get_develop_param_range'. It mentions 'where available' but doesn't specify context or exclusions, leaving usage unclear relative to siblings.

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