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

rawtherapee-mcp-server

by lucamarien
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

read_profile

Inspect a RawTherapee PP3 profile to view its settings before applying it to an image.

Instructions

Display contents of a PP3 profile in human-readable format.

Use this to inspect what settings a profile contains before applying it. Returns all active sections and their key-value pairs. Params: profile_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": {
      "profile_path": "<profile_path>"
    },
    "name": "read_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
profile_pathYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.4

TDQS

A3.7/5.0
Behavior3/5

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

The description indicates returns all sections and key-value pairs, but does not explicitly state it is non-destructive, which is important given no annotations. However, the read-only nature is implied.

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?

The description is mostly concise with three focused sentences, but the redundant 'Params: profile_path' line marginally harms structure.

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?

For a simple tool with output schema, the description covers purpose and return value but lacks parameter details and behavioral assurances like non-destructiveness.

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?

The description only mentions the parameter name without describing its format or constraints, despite 0% schema coverage, so it adds minimal value beyond the 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 the tool displays a PP3 profile in human-readable format for inspection, differentiating it from sibling tools that modify or compare profiles.

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 explicitly recommends using this tool to inspect profiles before applying, providing clear context. It does not contrast with siblings but the use case is well-defined.

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