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

rawtherapee-mcp-server

by lucamarien
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

adjust_crop_position

Reposition an existing crop area in a RAW photo profile to a new position using named coordinates or pixel offsets, updating the profile in-place.

Instructions

Reposition an existing crop within the source image bounds.

Moves the crop area defined in a PP3 profile to a new position. Accepts named positions ('left', 'center', 'right' for horizontal; 'top', 'center', 'bottom' for vertical) or pixel offsets as strings. The profile is updated in-place. Params: profile_path, file_path, horizontal, vertical, include_preview, preview_max_width

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>",
      "file_path": "<file_path>"
    },
    "name": "adjust_crop_position"
  }
}

Input Schema

NameRequiredDescriptionDefault
profile_pathYes
file_pathYes
horizontalNocenter
verticalNocenter
include_previewNo
preview_max_widthNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.4

TDQS

A3.6/5.0
Behavior3/5

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

The description discloses that the profile is updated in-place and accepts named positions or pixel offsets, but lacks details on bounds checking, success/failure signals, or side effects. With no annotations, additional behavioral context would be beneficial.

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?

The description is concise at four sentences with front-loaded purpose. The parameter list at the end is helpful, though slightly redundant. Could be more tightly structured.

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?

The description covers the core action but omits return value, error scenarios, and interaction with other tools. Given 6 parameters and no output schema, it is adequate but not comprehensive.

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 explains horizontal and vertical (named positions or offsets) but only lists other parameters without elaboration. This provides partial meaning but is insufficient for all six parameters.

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 clearly states the tool's action ('reposition an existing crop') and the resource ('PP3 profile'), distinguishing it from sibling tools like adjust_local_spot or adjust_profile. The verb is specific and the scope is well-defined.

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

Usage Guidelines3/5

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

The description implies usage for repositioning crops but does not specify when to use this tool versus alternatives like adjust_profile or analyze_image. No exclusion criteria or prerequisites are mentioned, leaving guidance implicit.

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