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

rawtherapee-mcp-server

by lucamarien
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

save_template

Save an existing PP3 profile as a custom template for reuse with apply_template or as a base for generate_pp3_profile.

Instructions

Save an existing PP3 profile as a reusable custom template.

Use this to save a tuned profile so it can be reused later with apply_template or as a base_template for generate_pp3_profile. Params: profile_path, name, description

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

Input Schema

NameRequiredDescriptionDefault
profile_pathYes
nameYes
descriptionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.4

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It does not mention whether saving overwrites existing templates, permission requirements, or side effects. Only that it saves, which is already implied by the name.

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

Conciseness3/5

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

The description is concise but includes redundancy (e.g., 'Save an existing PP3 profile' and 'save a tuned profile'). The parameter list is embedded in a sentence rather than formatted, reducing readability.

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?

An output schema exists, so return values are covered. However, the description omits prerequisites (e.g., profile existence) and error behavior (e.g., duplicate names). While functional, it leaves gaps for a complete understanding.

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 description coverage is 0%, so the description should add meaning to parameters. It merely lists parameter names (profile_path, name, description) without explaining their purpose, format, or constraints, such as the required path or uniqueness of name.

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 explicitly states 'Save an existing PP3 profile as a reusable custom template,' providing a specific verb and resource. It distinguishes the tool from siblings by mentioning reuse with 'apply_template' and 'generate_pp3_profile'.

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?

It advises use for saving tuned profiles for later reuse and names specific alternatives (apply_template, generate_pp3_profile). However, it does not explicitly mention when not to use this tool.

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