Skip to main content
Glama

match_photo_to_dna

Auto-compensates exposure and white balance in a Color DNA profile to match a target photo, then compiles a tailored Lightroom .xmp preset and optional Before/After comparison.

Instructions

Auto-compensate Exposure and White Balance of a Color DNA profile to match a target photo's lighting, then compile a tailored .xmp preset and optional Before/After comparison image.

Args: image_path: Path to the target photo (.jpg, .png, .webp). dna_id: Base Color DNA ID from the catalog. output_xmp_path: Destination path for the compiled .xmp file. preset_name: Display name inside Lightroom. slider_overrides: Optional manual slider adjustments applied after auto-matching. preview_output_path: Optional destination path for the Before/After JPEG comparison. 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": {
      "image_path": "<image_path>",
      "dna_id": "<dna_id>",
      "output_xmp_path": "<output_xmp_path>"
    },
    "name": "match_photo_to_dna"
  }
}

Input Schema

NameRequiredDescriptionDefault
dna_idYes
image_pathYes
preset_nameNoChromaDNA Matched
catalog_pathNo
output_xmp_pathYes
slider_overridesNo
preview_output_pathNo

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 supplied, the description carries the full behavioral burden, and it does disclose the side effects: it writes an .xmp file to output_xmp_path and optionally a comparison JPEG. It omits important operational details such as whether existing files are overwritten, whether the catalog must pre-exist, whether image_path is validated, and what happens on mismatch. Return values need no explanation because an output schema exists.

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 behavior is front-loaded in the first sentence, and the Args block is a compact, scannable list. It is somewhat long but every line corresponds to a real parameter, so nothing is obviously wasteful. Minor overlap with the schema's own field names is acceptable given the 0% coverage.

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 seven-parameter, multi-step tool with an output schema, the definition explains the pipeline, all inputs, and the two produced artifacts, which is most of what an agent needs. The gaps are operational rather than semantic: overwrite behavior, catalog preconditions, and failure modes are unaddressed in the absence of annotations.

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 is doing real work: it explains that image_path accepts .jpg/.png/.webp, dna_id must come from the catalog, preset_name is the Lightroom display name, slider_overrides are applied after auto-matching, and catalog_path points at color_dna_catalog.json. This meaningfully exceeds the bare titles in the schema, though ordering/format details for slider_overrides keys are left unstated.

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 names a concrete pipeline: auto-compensate exposure and white balance of a Color DNA profile against a target photo, then compile an .xmp preset plus an optional Before/After JPEG. That is a specific verb-plus-resource statement an agent can act on. It does not, however, distinguish itself from siblings like compile_xmp_preset or render_preview, whose names suggest overlapping output artifacts.

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 explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. The only usage signal is implicit in the workflow phrasing ('to match a target photo's lighting'), which tells the agent the scenario but not how to choose this over compile_xmp_preset or render_preview.

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