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

rawtherapee-mcp-server

by lucamarien
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

apply_template

Apply a predefined PP3 template to a RAW file for quick processing with a specific style. Optionally add a device preset for crop/resize and get an inline preview.

Instructions

Apply a built-in or custom PP3 template to a RAW file and process it.

Use this for quick processing with a predefined style. Optionally apply a device preset for crop/resize on top of the template. Returns an inline thumbnail when include_preview is True. Params: file_path, template_name, output_format, output_dir, device_preset, 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": {
      "file_path": "<file_path>",
      "template_name": "<template_name>"
    },
    "name": "apply_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYes
template_nameYes
output_formatNojpeg
output_dirNo
device_presetNo
include_previewNo
preview_max_widthNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.4

TDQS

A3.5/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It mentions returning an inline thumbnail when include_preview is True, but does not disclose side effects like file output behavior or whether the original is modified. Missing key behavioral details for a processing tool.

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?

Two concise sentences plus a parameter list. The list is somewhat redundant but helpful. Front-loaded with purpose. Could be slightly more concise by integrating parameter details.

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

Completeness2/5

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

With 7 parameters, no output schema, and no annotations, the description is too sparse. It explains only a few parameters and omits details on defaults, behavior of output_dir, preview_max_width, and return values beyond the thumbnail.

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%. The description adds meaning for template_name (built-in or custom), device_preset (crop/resize), and include_preview (returns thumbnail). Other parameters like file_path, output_format, output_dir, preview_max_width lack explanation.

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 applies a PP3 template to a RAW file for quick processing with a predefined style. It distinguishes itself from sibling tools like 'apply_local_preset' or 'apply_lut' by focusing on full templates.

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 says 'Use this for quick processing with a predefined style', providing a clear when-to-use. However, it does not mention when not to use or contrast with alternative tools like 'process_raw'.

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