Skip to main content
Glama

analyze_photo

Analyze a photo's luminance, dynamic range, and RGB color cast to get ranked Color DNA recommendations for matching Lightroom/Camera Raw color looks.

Instructions

Analyze an input photo's luminance, dynamic range, and RGB color cast, and recommend matching Color DNAs.

Args: image_path: Path to the target photo (.jpg, .png, .webp). top_k: Number of recommended Color DNA profiles to return (default: 3). 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>"
    },
    "name": "analyze_photo"
  }
}

Input Schema

NameRequiredDescriptionDefault
top_kNo
image_pathYes
catalog_pathNo

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, the description carries the full behavioral burden. It discloses the analysis dimensions, recommendation behavior, and supported image formats, but does not explicitly state that it is read-only, whether it requires local file access, or how errors are handled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose and follows with a compact Args block. Every sentence and argument entry adds useful information without unnecessary wording.

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?

The tool has an output schema, so return values need not be explained. The description covers the three parameters and the main analysis behavior, though it could say more about read-only behavior and usage relative to alternatives.

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 description must compensate, and it does: image_path is explained with supported extensions, top_k is explained as the number of recommended profiles with its default, and catalog_path is described as an optional custom catalog path. Minor gaps remain, such as top_k bounds or catalog file requirements.

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 states a specific verb and resource: analyze a photo's luminance, dynamic range, and RGB color cast, then recommend matching Color DNAs. It is clear enough to understand what the tool does, but it does not explicitly differentiate itself from similarly named sibling tools such as match_photo_to_dna.

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?

The description does not say when to use this tool rather than alternatives, nor does it state exclusions or prerequisites. Usage is only implied by the action described in the first sentence.

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