Skip to main content
Glama
baramesh

Photoshop MCP Elite

by baramesh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

photoshop_harmonize_sky

Replace and harmonize skies in Photoshop: AI-selects sky, inserts new sky, adds horizon haze, and relights foreground for natural blending.

Instructions

Seamlessly replaces and harmonizes sky: 1. Uses Sensei AI Select Sky for precise architectural contour isolation. 2. Places and scales replacement sky image. 3. Adds atmospheric horizon haze gradient layer to blend background naturally. 4. Automatically relights foreground subjects with warm ambient light to match the sky.

Args:
    sky_image_path: Local path to sky replacement image.
    haze_opacity: Opacity percentage (0-100) for horizon atmospheric haze.
    sky_opacity: Opacity percentage (0-100) for sky layer.
    warm_foreground: If True, warms non-sky foreground subjects with light tone curve matching.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sky_opacityNo
haze_opacityNo
sky_image_pathYes
warm_foregroundNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it describes a multi-step internal process (AI selection, layer placement, haze gradient, relighting), which informs the agent about side effects and complexity. It doesn't mention permissions, performance cost, or reversibility, but the process transparency is strong for a creative tool.

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 description is front-loaded with a clear purpose statement followed by numbered steps and a parameter list. It is a bit verbose (the step list could be trimmed), but every sentence conveys useful information and the structure is easy to parse.

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?

Given a 4-parameter tool with no annotations and an output schema (which handles return values), the description provides sufficient process and parameter detail for an agent to invoke correctly. The only gap is usage guidance relative to alternatives, which is covered under usage_guidelines.

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 supply parameter meaning. It explains each parameter's role and gives ranges/defaults for opacity parameters ('Opacity percentage (0-100)'), and clarifies 'warm_foreground' as warming non-sky foreground subjects. This adds substantial value beyond the bare-named schema properties.

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 clearly states a specific verb ('replaces and harmonizes') and resource ('sky'), then enumerates the exact pipeline steps. It is distinguishable from siblings like photoshop_select_sky (which only selects) and photoshop_match_lighting_and_tone (generic relighting).

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 explains what the tool does but provides no guidance on when to use it versus alternatives such as photoshop_select_sky combined with manual compositing, or photoshop_match_lighting_and_tone. No context, prerequisites, or exclusions are given.

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

Deploy Server

Other Tools