Skip to main content
Glama

bundled_qwen_image_2512_with_lora_json

Generate images using a Qwen-Image workflow with LoRA support. Customize resolution, prompt, and LoRA parameters for controlled outputs.

Instructions

Comfy image generation workflow qwen_image_2512_with_lora.json

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cfgNo
seedNo
typeNoqwen_image
shiftNo
stepsNo
widthNo
heightNo
denoiseNo
vae_nameNoqwen_image_vae.safetensors
clip_nameNoqwen_2.5_vl_7b_fp8_scaled.safetensors
lora_nameNoQwen-Image-2512-Lightning-4steps-V1.0-fp32.safetensors
schedulerNosimple
unet_nameNoqwen_image_2512_fp8_e4m3fn.safetensors
batch_sizeNo
output_dirNo
CLIP___textNorealistic, photorealistic, human proportions, blurry, deformed, ugly, low quality, watermark, text
sampler_nameNoeuler
submit_batchNo
weight_dtypeNodefault
batch_by_timeNo
strength_clipNo
strength_modelNo
filename_prefixNoqwen-2512
Behavior1/5

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

No annotations provided, and the description lacks any behavioral details such as side effects, authentication needs, or operational constraints. The description is essentially empty.

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

Conciseness1/5

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

While short, the sentence is uninformative and does not justify its existence. It is under-specified, not concise.

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

Completeness1/5

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

Given 23 parameters, no output schema, and no annotations, the description is critically incomplete. It fails to explain inputs, outputs, or purpose.

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

Parameters1/5

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

Schema coverage is 0% (description adds no parameter info) and there are 23 parameters with defaults but no explanations. The description does not compensate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Comfy image generation workflow' identifies the domain but does not specify what the tool does beyond restating the file name. It fails to distinguish from sibling tools like 'bundled_image_z_image_turbo_json'.

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 use this tool versus alternatives. Context for usage is absent.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bookandmusic/mcp-comfyui'

If you have feedback or need assistance with the MCP directory API, please join our Discord server