Skip to main content
Glama
Sign In
rawtherapee-mcp-server

rawtherapee-mcp-server

by lucamarien
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_local_adjustments

List each local adjustment spot in a PP3 profile, showing name, type, luminance range, active parameters, and enabled state for inspection before editing.

Instructions

List all Locallab (local adjustment) spots in a PP3 profile.

Shows each spot's name, type, luminance range, active parameters, and enabled state. Use this to inspect the local adjustments before previewing or modifying them.

Params: profile_path

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "profile_path": "<profile_path>"
    },
    "name": "list_local_adjustments"
  }
}

Input Schema

NameRequiredDescriptionDefault
profile_pathYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.4

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided, so description must describe behavior. It implies read-only via 'list' but does not explicitly confirm non-destructiveness or mention auth/rate limits. Adequate but could be more explicit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

Concise three sentences that front-load purpose and list output fields. The 'Params: profile_path' line is slightly redundant but not harmful. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given one required parameter and existence of output schema (context signal), description covers main points: what it does, what it returns, and when to use. Could mention prerequisites like file existence, but generally complete.

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 coverage is 0% with no parameter description. Description only mentions 'profile_path' without explaining what it is (e.g., path to .pp3 file). Adds minimal value beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description starts with a specific verb ('List') and resource ('all Locallab spots'), and clarifies output details. It distinguishes from sibling tools like remove_local_adjustment and adjust_local_spot by focusing on inspection.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states 'Use this to inspect local adjustments before previewing or modifying them', giving clear context for when to use. Lacks explicit exclusions but implies appropriate timing.

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