rawtherapee-mcp-server

Overview Schema Source Related Servers Discussions Admin

create_template_from_description

Converts a natural language description of a desired photo look into a RawTherapee PP3 template for consistent image processing.

Instructions

Create a new PP3 template from a natural language style description.

Use this to create a template when the user describes a look in words (e.g. "warm golden hour tones, film-like grain"). You (Claude) interpret the description and call generate_pp3_profile with appropriate parameters. This tool creates a neutral base template with the given name and description. Params: name, description, reference_image_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": {
      "name": "<name>",
      "description": "<description>"
    },
    "name": "create_template_from_description"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`description`	Yes
`reference_image_path`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.4May 26, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. It states it creates a neutral base template and mentions the AI's role in calling generate_pp3_profile, but does not disclose side effects (e.g., saving, permissions) or details on what 'creates' implies. Moderate transparency.

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?

Each sentence adds value: purpose, usage scenario, interpretation process, and parameter list. No wasted words, front-loaded with purpose. The description is concise and well-structured.

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?

Covers purpose, usage, and parameters. With an output schema present (not shown), return values are likely documented. Could include more on behavioral details (e.g., saving), but overall adequate for the tool's simplicity.

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

Parameters4/5

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

Schema coverage is 0%, but the description lists all three parameters and adds context: 'description' is a natural language style, 'name' is the template name, and 'reference_image_path' is optional with default null. This goes beyond the bare 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 clearly states it creates a new PP3 template from a natural language description. It differentiates from sibling tools like 'generate_pp3_profile' by noting that this tool creates a neutral base template and then the AI interprets the description and calls the profile generator.

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 to create a template when the user describes a look in words' with an example. It lacks explicit when-not-to-use or comparison to alternatives, but the context and sibling list provide enough differentiation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server