Skip to main content
Glama

compile_xmp_preset

Compile a Color DNA profile and optional Camera Raw slider overrides into a valid Adobe Camera Raw .xmp preset for Lightroom, avoiding filename collisions with RAW files.

Instructions

Compile a Color DNA profile (with optional custom slider tweaks) into a valid Adobe Camera Raw .xmp file.

Args: dna_id: Color DNA ID from the catalog. preset_name: Preset display name inside Lightroom. output_xmp_path: Destination .xmp file path (must not collide with an existing RAW file stem). group_name: Preset folder/group name inside Lightroom (default: "ChromaDNA"). slider_overrides: Optional dict of Camera Raw slider adjustments. catalog_path: Optional custom path to color_dna_catalog.json.

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": {
      "dna_id": "<dna_id>",
      "preset_name": "<preset_name>",
      "output_xmp_path": "<output_xmp_path>"
    },
    "name": "compile_xmp_preset"
  }
}

Input Schema

NameRequiredDescriptionDefault
dna_idYes
group_nameNoChromaDNA
preset_nameYes
catalog_pathNo
output_xmp_pathYes
slider_overridesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose that this writes a file to a caller-supplied path and that the path must not collide with a RAW file stem. It does not say what happens if an .xmp already exists at that path, whether it overwrites, or what filesystem permissions are required.

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 core action is front-loaded in the first sentence, followed by a compact per-parameter list where every line carries information. Slightly list-heavy but nothing is redundant.

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?

For a 6-parameter file-writing tool with no annotations, the description covers purpose and every parameter's role, and an output schema exists so return values need not be explained. The remaining gap is failure/overwrite behaviour at the destination path.

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 description coverage is 0%, so the Args block does the heavy lifting: it explains dna_id's source (the catalog), that preset_name is the Lightroom display name, that group_name is the Lightroom folder with a default, and that slider_overrides is an optional dict of Camera Raw slider adjustments. That is meaningfully more than the bare schema titles.

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?

States a specific verb and resource: compiles a Color DNA profile into an Adobe Camera Raw .xmp file. That is distinct from siblings like export_cube_lut or render_preview, though the description never names an alternative to contrast against.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to choose this over export_cube_lut (another export path) or render_preview. The only constraint given is that output_xmp_path must not collide with an existing RAW stem, which is a constraint rather than when-to-use direction.

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