Skip to main content
Glama

bundled_sensenova_json

Generate images by executing a ComfyUI workflow from a text prompt. Configure parameters like steps, seed, and dimensions to control output.

Instructions

Comfy image generation workflow sensenova.json

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cfgNo
seedNo
stepsNo
promptNo这是一张主题为"夏日清凉指南"的信息图,采用16:9宽高比,4K分辨率,面向大众读者,旨在提供实用的夏季避暑建议。整体风格为现代扁平化设计,配色以清凉的浅蓝色、薄荷绿和白色为主,背景采用带有轻微纸张纹理的浅灰色,营造清爽舒适的视觉氛围。构图采用Bento网格布局,分为五个主要模块,每个模块用圆角矩形框区分,模块间通过细线分隔,留白充足。 ## 整体布局 - 顶部标题区:大字号主标题"夏日清凉指南",副标题"避暑全攻略",居中对齐,字体采用无衬线粗体,颜色为深蓝色。 - 主体区:采用2x3网格布局,包含五个内容模块: 1. 左上:"避暑胜地推荐" - 用地图图标和列表展示推荐地点 2. 右上:"防暑小贴士" - 用盾牌图标和要点列表展示防护措施 3. 左中:"清凉饮品推荐" - 用饮料图标和卡片展示饮品类型 4. 右中:"避暑装备清单" - 用背包图标和清单展示必备物品 5. 底部:"中暑急救指南" - 用急救十字图标和流程图展示急救步骤 - 每个模块包含:图标(扁平化风格,蓝色系)、标题(加粗)、内容(列表或简短说明)、装饰性元素(如小太阳、水滴、树叶等夏日元素)。 ## 背景与风格 - 背景:浅灰色纸张纹理,带有细微的网格线 - 风格:现代扁平化设计,简洁明快 - 配色:主色调为浅蓝色、薄荷绿、白色,强调色为橙色用于高亮重要信息 - 字体:中文采用思源黑体,英文采用Roboto ## 内容分区 ### 分区1: 避暑胜地推荐 - 视觉元素:山脉图标、温度计图标(显示低温)、列表项图标 - 文字标签:"避暑胜地推荐"、"高山地区"、"海滨城市"、"森林景区" - 数据呈现:用地图轮廓和地点标记展示推荐区域 ### 分区2: 防暑小贴士 - 视觉元素:盾牌图标、太阳图标(带斜杠)、水滴图标 - 文字标签:"防暑小贴士"、"避免正午外出"、"多补充水分"、"穿着透气衣物" - 数据呈现:用图标+短句的形式展示 ### 分区3: 清凉饮品推荐 - 视觉元素:饮料杯图标、西瓜图标、柠檬图标 - 文字标签:"清凉饮品推荐"、"绿豆汤"、"柠檬水"、"凉茶" - 数据呈现:用饮品卡片展示,每张卡片包含饮品名称和简短描述 ### 分区4: 避暑装备清单 - 视觉元素:背包图标、遮阳伞图标、防晒霜瓶子图标 - 文字标签:"避暑装备清单"、"遮阳帽"、"防晒霜"、"便携风扇" - 数据呈现:用清单形式展示,每项前带复选框图标 ### 分区5: 中暑急救指南 - 视觉元素:急救十字图标、流程图箭头、人物图标 - 文字标签:"中暑急救指南"、"移至阴凉处"、"补充水分"、"必要时就医" - 数据呈现:用流程图形式展示急救步骤,箭头连接各步骤 ## 视觉细节 - 字体:主标题32pt粗体,副标题24pt,模块标题18pt粗体,正文14pt - 图标:统一使用扁平化线性图标,线条粗细一致,颜色为深蓝色 - 连接线:模块间用浅灰色细线分隔,流程图用蓝色箭头连接 - 留白:每个模块内部留白充足,模块间距为20px - 装饰元素:角落点缀小太阳、水滴、树叶等夏日元素,增加氛围感
img_cfgNo
batch_sizeNo
output_dirNo
submit_batchNo
batch_by_timeNo
target_pixelsNo16:9
filename_prefixNoComfyUI
Behavior1/5

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

No annotations provided, and the description fails to disclose any behavioral traits such as side effects, authentication requirements, rate limits, or what happens to input/output. The word 'workflow' hints at complexity but nothing concrete.

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

Conciseness2/5

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

The description is a single, under-specified phrase. It is too short to be helpful; 'conciseness' implies efficiency without loss of meaning, but this sacrifices essential information.

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 11 parameters, no output schema, and no annotations, the description is wholly inadequate. It provides no information on how the workflow behaves, what it outputs, or how to use it effectively.

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 description coverage is 0% across 11 parameters, and the description adds no explanation for parameters like 'submit_batch', 'batch_by_time', 'target_pixels', or 'filename_prefix'. The description does not compensate for the missing schema descriptions.

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 sensenova.json' is a noun phrase without a verb. It vaguely suggests image generation but does not state an action (e.g., 'Generates images using...') or distinguish from sibling tools like bundled_image_z_image_turbo_json or bundled_qwen_image_2512_with_lora_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 vs alternatives. Sibling tools perform similar image tasks, but the description gives no decision criteria or context.

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