Skip to main content
Glama

blend_color_dna

Blend two or more Color DNA profiles by weight to interpolate sliders and Tone Curves, then compile the hybrid look into an Adobe Lightroom .xmp preset.

Instructions

Mathematically blend 2 or more Color DNA profiles by weight (interpolating sliders & Tone Curves) and compile the hybrid style into an Adobe Lightroom .xmp preset.

Args: weights: Mapping of Color DNA ID to weight, e.g. {"film_emulation_001": 0.7, "cinematic_teal_orange_002": 0.3}. preset_name: Display name of the preset inside Lightroom. output_xmp_path: Destination path for the compiled .xmp file. slider_overrides: Optional dict of slider tweaks applied after blending (e.g., {"GrainAmount": 12}). preview_image_path: Optional source photo path to generate a Before/After JPEG preview. preview_output_path: Optional destination path for the Before/After preview JPEG. 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": {
      "weights": "<weights>",
      "preset_name": "<preset_name>",
      "output_xmp_path": "<output_xmp_path>"
    },
    "name": "blend_color_dna"
  }
}

Input Schema

NameRequiredDescriptionDefault
weightsYes
preset_nameYes
catalog_pathNo
output_xmp_pathYes
slider_overridesNo
preview_image_pathNo
preview_output_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It does add useful detail beyond the schema: blending interpolates sliders and Tone Curves, and the result is written to a destination .xmp path, with an optional Before/After JPEG preview. It does not disclose overwrite behavior for an existing output_xmp_path, what happens if a Color DNA ID is unknown, whether weights are normalized, or any permission/path-validity constraints, which are meaningful gaps for a write operation on a user-specified file.

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 operation is front-loaded in the first sentence, and the Args block is a compact, scannable enumeration with no filler prose. The docstring 'Args:' framing is slightly verbose but earns its place given zero schema descriptions.

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 seven-parameter tool that performs mathematical blending, file compilation, and optional image rendering, the definition covers inputs and the primary output artifact well, and the existence of an output schema relieves it of explaining return values. It is still thin on operational edge cases: weight normalization, invalid DNA IDs, and output-file overwrite semantics are unaddressed, which matters for a tool that writes to user-specified paths.

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 section does the heavy lifting and mostly succeeds: it explains the weights mapping with a concrete weighted example, names the preset_name's role in Lightroom, describes each path parameter's purpose, and clarifies that slider_overrides are applied after blending. Minor gaps remain, such as whether weights must sum to 1 and what catalog_path's default resolution is, keeping it below a 5.

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 states a specific verb chain (blend mathematically, then compile into an .xmp preset) on a specific resource (Color DNA profiles), plus the exact output artifact an Adobe Lightroom .xmp file. An agent can distinguish this from compile_xmp_preset because the blending of multiple DNA profiles by weight is called out as the core operation.

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

Usage Guidelines3/5

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

Usage is implied by 'blend 2 or more Color DNA profiles by weight' and by the optional preview parameters, so an agent knows the context in which the tool applies. However, there is no explicit when-to-use versus when-not guidance and no mention of the sibling tools (match_photo_to_dna, compile_xmp_preset) that would route an agent deciding between blending and direct compilation.

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