Skip to main content
Glama

render_preview

Generate a side-by-side Before/After JPEG preview of a Color DNA applied to an image, with optional slider overrides, without using Lightroom.

Instructions

Render a fast side-by-side Before/After JPEG preview applying a Color DNA onto an image without Lightroom.

Args: image_path: Source photo path (.jpg, .png, .webp). dna_id: Color DNA ID to simulate. output_preview_path: Destination JPEG path for the Before/After comparison. slider_overrides: Optional slider tweaks to preview before exporting XMP. 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_preview_path": "<output_preview_path>"
    },
    "name": "render_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
dna_idYes
image_pathYes
catalog_pathNo
slider_overridesNo
output_preview_pathYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/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 burden and does disclose the key side effect: a JPEG is written to output_preview_path, and no Lightroom is required. It omits overwrite behavior, whether existing files are clobbered, error/permission cases, and how long a 'fast' render takes on large inputs.

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 sentence is front-loaded and states purpose, speed, output type, and the no-Lightroom constraint immediately; the Args list is scan-friendly. Slight redundancy between the summary sentence and the arg glosses, but nothing is wasted.

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?

Five parameters with three required is well covered, and the presence of an output schema means return values need no explanation here. What remains thin is the behavior on a mutation tool with no annotations - overwrite/permission semantics and slider_overrides key vocabulary are still absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 gives accepted image extensions (.jpg, .png, .webp), explains dna_id is the profile to simulate, and that catalog_path overrides color_dna_catalog.json. However, several lines merely restate the parameter name in sentence form, and the accepted key set for slider_overrides is never described.

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?

Names a specific verb and artifact: 'Render a fast side-by-side Before/After JPEG preview applying a Color DNA onto an image.' The 'without Lightroom' clause plus the JPEG-preview framing distinguishes it from a full export or blend, though it never names which sibling to use instead.

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?

The slider_overrides line implies the intended workflow ('preview before exporting XMP'), so an agent can infer this is a pre-flight check ahead of preset compilation. There is no explicit statement of when to skip this tool or which sibling handles the export itself.

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