Skip to main content
Glama
Sign In
genart-dev

genart-mcp

by genart-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

design_adjust_hsl

Create or update an HSL adjustment layer to shift hue, saturation, and lightness, with optional targeting by hue range for precise color edits.

Instructions

Create or update an HSL adjustment layer.

Input Schema

NameRequiredDescriptionDefault
hueNoHue rotation −180–180. Default 0.
layerIdNoUpdate existing layer (creates new if omitted).
opacityNo
layerNameNo
lightnessNoLightness offset −100–100. Default 0.
targetHueNoRestrict to pixels near this hue (deg). −1 = all colors.
saturationNoSaturation offset −100–100. Default 0.
targetRangeNoHue range degrees. Default 30.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It says 'create or update' but doesn't disclose where the layer is inserted, whether an update overwrites prior HSL settings, whether the operation is reversible, or what happens on target-range edits. For a mutation tool with zero annotation coverage this is a significant gap.

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?

A single efficient sentence with the create/update operation front-loaded. It is not padded, though it is arguably too terse for an 8-parameter mutation tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 8 parameters, no annotations, and no output schema, the description should explain the create-vs-update behavior and the scoping of targetHue/targetRange to hue edits. It doesn't, so the definition is not complete enough for reliable invocation.

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 75%, with hue, lightness, saturation, targetHue and targetRange ranges documented in the schema. The description adds no parameter meaning beyond that; opacity and layerName remain bare in both schema and description. Baseline 3 is appropriate given the schema carries most of the load.

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?

States a specific verb ('Create or update') and resource ('HSL adjustment layer'), so an agent knows the operation. However it gives no differentiation from the many sibling adjustment tools (design_adjust_levels, design_adjust_curves, design_adjust_color_balance, design_apply_gradient_map), leaving the agent to infer which adjustment to pick.

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?

No guidance on when to choose HSL over the other adjustment tools, nor on the create-vs-update branching beyond what the layerId schema already implies. The agent gets no context for prerequisites or alternatives.

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