Skip to main content
Glama
lucamarien

rawtherapee-mcp-server

by lucamarien

adjust_profile

Modify specific parameters in an existing PP3 profile, changing only desired settings while preserving all others.

Instructions

Modify specific parameters in an existing PP3 profile.

Use this to tweak individual settings without recreating the entire profile. Only the specified parameters are changed; all other settings are preserved.

Accepts both friendly parameter names (e.g. {"crop": {"width": 3108}}) and raw PP3 section/key pairs (e.g. {"Crop": {"W": "3108", "H": "6732"}}). Unrecognized group names are treated as raw PP3 section names. Params: profile_path, adjustments, save_as

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profile_pathYes
adjustmentsYes
save_asNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Discloses that only specified parameters change and others are preserved, and explains dual input formats; but does not mention error handling or validation behavior.

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?

Reasonably concise with a clear structure—purpose, usage, behavior, parameter details—but could be slightly more streamlined.

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

Completeness5/5

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

Given the parameter complexity and absence of annotations, the description covers purpose, usage, behavior, and parameter semantics comprehensively; output schema exists so return values need not be explained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Provides examples and explains that adjustments can be friendly or raw PP3 section/key pairs, adding significant meaning beyond the schema which has 0% description coverage.

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?

Clearly states it modifies specific parameters in an existing PP3 profile, distinguishing it from creation (generate_pp3_profile) and read-only (read_profile) tools.

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 recommends use for tweaking individual settings without recreating the entire profile, though no explicit when-not-to-use or alternatives are mentioned beyond the sibling list.

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/lucamarien/rawtherapee-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server