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

rawtherapee-mcp-server

by lucamarien
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_device_preset_tool

Create and save custom cropping and resizing presets for devices or formats not included in the default list, available across sessions.

Instructions

Create and persist a custom device/format preset for cropping and resizing.

Use this to add a preset for a device or format not in the built-in list. Custom presets are saved to disk and available in future sessions. Params: preset_id, name, width, height, category

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": {
      "preset_id": "<preset_id>",
      "name": "<name>",
      "width": "<width>",
      "height": "<height>"
    },
    "name": "add_device_preset_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
preset_idYes
nameYes
widthYes
heightYes
categoryNocustom

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.4

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description discloses that 'Custom presets are saved to disk and available in future sessions,' which adds valuable behavioral context. No conflicts with annotations.

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?

The description is concise (4 sentences) with each sentence serving a clear purpose: purpose, when to use, behavior, and parameter list. No unnecessary words.

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?

For a simple creation tool with an output schema, the description covers purpose, usage guidance, persistence, and parameter list. It is complete given the tool's straightforward nature.

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?

Despite 0% schema description coverage, the description lists the parameters (preset_id, name, width, height, category). However, it provides no additional details like units or constraints, so only partially compensates.

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 'Create and persist a custom device/format preset for cropping and resizing,' providing a specific verb and resource. It distinguishes from siblings like list_device_presets and delete_device_preset.

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?

The description says 'Use this to add a preset for a device or format not in the built-in list,' giving clear context for when to use the tool. However, it does not explicitly mention when not to use it or suggest alternatives.

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