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

rawtherapee-mcp-server

by lucamarien
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_device_preset

Delete a custom device preset. Removes only user-created presets; built-in presets are protected.

Instructions

Delete a custom device preset.

Use this to remove a custom device preset. Built-in presets cannot be deleted. Params: preset_id

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": "delete_device_preset"
  }
}

Input Schema

NameRequiredDescriptionDefault
preset_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.4

TDQS

B3.4/5.0
Behavior3/5

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

The description indicates a destructive action (delete) and notes a restriction (only custom presets), but lacks details on reversibility, permissions, or side effects. With no annotations, the description carries full burden and is minimally adequate.

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 relatively short but includes a redundant 'Params: preset_id' line that adds no new information, reducing conciseness.

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?

Given only one parameter and an existing output schema, the description covers core functionality and restrictions. It is mostly complete for a simple deletion tool.

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 coverage is 0%, so the description must add meaning. It merely lists 'preset_id' without explaining its role or format, adding no value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('delete') and the resource ('custom device preset'), and distinguishes it from built-in presets. It is specific and actionable.

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 instructs to use for custom presets and warns that built-in presets cannot be deleted, providing clear guidance on when to use and when not.

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