Skip to main content
Glama

style_transfer

Applies the artistic style of a reference image to new or existing images while preserving the content structure. Use it to transform photos, unify visual aesthetics, or blend multiple style references.

Instructions

Apply artistic style from a reference image to new or existing content while preserving the content structure.

Use this when:

  • Applying artistic styles to new image generations

  • Transforming existing images with a reference style

  • Creating consistent visual aesthetics across multiple images

  • Blending multiple style references together

  • Analyzing style characteristics before generation

NOT for:

  • Character consistency across poses (use generate_character_set instead)

  • Simple image editing (use edit_image instead)

  • Generating images from scratch without style reference (use generate_image instead)

Chain with: If user requests specific pixel dimensions for styled images, chain with resize_image after generation.

Example: "style_transfer referenceStyleImage='./van-gogh.jpg' contentDescription='mountain landscape at sunset' styleStrength=0.8"

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": {
      "styleStrength": "<styleStrength>",
      "outputFormat": "<outputFormat>",
      "quality": "<quality>",
      "aspectRatio": "<aspectRatio>",
      "size": "<size>",
      "analyzeStyleOnly": "<analyzeStyleOnly>"
    },
    "name": "style_transfer"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeYes2k
qualityYes
aspectRatioYes1:1
contentImageNo
outputFormatYespng
styleAspectsNo
styleStrengthYes
outputFilenameNo
analyzeStyleOnlyYes
preserveElementsNo
contentDescriptionNo
referenceStyleImageNo
referenceStyleImagesNo

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?

No annotations are supplied, so the description carries the full behavioral burden. It does add useful context — content structure is preserved, style can be analyzed without generating (analyzeStyleOnly), and up to three style references can be blended — but it never says what the tool returns (image path, filename, base64?) or what happens to existing files when outputFilename collides. That return/IO gap matters for a tool with no output schema.

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?

Well front-loaded: the one-line purpose comes first, followed by scannable when/not-for/chain sections and a concrete example. The structure is efficient, though the bulleted 'use this when' entries partially restate the opening sentence and could be tightened.

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?

For a 13-parameter tool with no annotations and no output schema, the definition covers routing well but leaves the mechanics thin: no return value, no indication of whether referenceStyleImage is required when generating new content, and no explanation of how styleStrength, styleAspects, and preserveElements interact. An agent can pick this tool but still has to guess at several required inputs.

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 13 parameters, so the description must compensate and largely does not. The example only illustrates referenceStyleImage, contentDescription, and styleStrength; size, quality, aspectRatio, outputFormat, outputFilename, styleAspects, preserveElements, contentImage, and referenceStyleImages are never explained, and the interplay between contentImage and contentDescription (existing vs. new content) is only implied.

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: applying artistic style from a reference image to new or existing content, with the constraint of preserving content structure. It explicitly distinguishes itself from generate_image, edit_image, and generate_character_set by name, so an agent can route correctly without opening a schema.

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, a 'NOT for' list naming the correct alternative for each excluded case, and a chaining rule (resize_image after generation when pixel dimensions are requested). Both the positive and negative routing conditions are spelled out.

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