Skip to main content
Glama

blend_images

Combine 2–4 images into a single AI-composed image using collage, double-exposure, or overlay blend modes.

Instructions

Blend multiple images together using AI-powered composition with various blend modes (seamless, collage, double-exposure, overlay).

Use this when:

  • Combining 2-4 images into a single composition

  • Creating seamless blends or artistic collages

  • Making double-exposure effects

  • Overlaying images with natural transitions

NOT for:

  • Editing a single image (use edit_image instead)

  • Generating images from scratch (use generate_image instead)

  • Simple format conversion (use convert_image instead)

  • Removing backgrounds only (use remove_background instead)

Example: "blend_images imagePaths=['./bg.jpg', './subject.png'] instruction='Place subject on background' blendMode='seamless'"

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": {
      "imagePaths": "<imagePaths>",
      "instruction": "<instruction>",
      "blendMode": "<blendMode>",
      "outputFormat": "<outputFormat>",
      "quality": "<quality>",
      "opacity": "<opacity>",
      "resizeBehavior": "<resizeBehavior>"
    },
    "name": "blend_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
opacityYes
qualityYes
blendModeYesseamless
imagePathsYes
aspectRatioNo
instructionYes
outputFormatYespng
outputFilenameNo
resizeBehaviorYescontain

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.2

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden. It usefully discloses the AI-composition nature and the 2-4 image limit, but says nothing about where the result goes (file path vs returned data), latency, whether the call is asynchronous, cost, or what happens on partial failure. The core intent is clear but operational behavior is only partially covered.

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?

Front-loads the operation, then bullets for when-to-use and when-not-to-use, then a concrete example — a clean, scannable structure. The trailing example mostly restates parameter names already implied earlier, so a small amount of content could be trimmed.

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?

This is a 9-parameter mutation-style tool with no annotations, no output schema and 0% schema coverage, so the description needed to carry much more. It never explains the return value or output location, and leaves the majority of parameters undefined, which is a real gap for an agent trying to call it correctly on the first attempt.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 9 parameters (7 required), so the description must compensate and largely doesn't. Only imagePaths, instruction and blendMode appear, and only inside the example string; opacity, quality, outputFormat, resizeBehavior, aspectRatio and outputFilename are never explained, including how opacity interacts with blendMode.

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?

States a specific verb and resource ("Blend multiple images together using AI-powered composition") and enumerates the four blend modes, so the agent knows exactly what operation this performs. It is clearly distinguishable from generate_image, edit_image, convert_image and remove_background, which are named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides an explicit "Use this when" list (2-4 image composition, seamless blends, double-exposure, overlays) and a "NOT for" list that routes each excluded case to a named sibling (edit_image, generate_image, convert_image, remove_background). This is exactly the when/when-not/alternatives structure that removes ambiguity.

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