designforyou

by org.swapp1990.designforyou

Generate VN sprite sheet

vn_generate_sprite_sheet

Generate one fixed-grid visual-novel character sprite sheet, crop it into cell assets, remove the chroma-key background, validate transparent sprites, and return a VN Creator-ready manifest. Base cost: 3 credits. Optional quality.hi_res_cells=true adds a reference-grounded per-cell re-render at full native resolution (fixes cells being limited to ~1/N of the sheet resolution) and bills +2 credits per cell re-rendered. quality.hi_res_model optionally routes the hi-res pass to a specific model (e.g. gpt-image-2 for fabric fidelity).

Input Schema

TableJSON Schema

Name	Required	Description
`cells`	Yes
`model`	No	Image model override for the source sheet, e.g. gemini-3.1-flash-image.
`sheet`	Yes
`style`	Yes
`output`	No
`quality`	No
`provider`	No	Image provider override for the source sheet, e.g. gemini, grok, or a known model alias.
`character`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedJul 5, 2026

addedInput schema / properties / quality / properties / hi_res_cells

Added value: +{
+  "default": false,
+  "description": "Opt-in: after cropping each cell from the consistency grid, run a reference-grounded image-to-image re-render of that cell at full native model resolution (the crop is the identity/pose reference). Fixes cells being limited to ~1/N of the sheet resolution. Billed as an extra image call per cell (+2 credits each).",
+  "title": "Hi Res Cells",
+  "type": "boolean"
+}

addedInput schema / properties / quality / properties / hi_res_model

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Optional model override for the per-cell hi-res re-render, e.g. gpt-image-2 for fabric fidelity. Defaults to the source sheet's provider/model. Accepts gemini, grok, and gpt-image-2 aliases.",
+  "title": "Hi Res Model"
+}

Changed1 schema field changedJun 29, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

First observedJun 24, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations are minimal (readOnly=false, destructive=false, openWorld=true), so the description carries the transparency burden. It discloses credit costs (base 3, +2 per hi-res cell), the background-removal behavior, the fixed-grid cropping, and the cell-resolution limitation that hi_res_cells addresses. This goes far beyond the structured annotations.

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

Conciseness5/5

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

The description is dense and front-loaded: the first sentence captures the full pipeline, and the optional hi-res details are placed after the base behavior. No filler or repeated schema information; every sentence adds material context like credits, resolution limits, or model override behavior.

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

Completeness5/5

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

Given the tool's complexity (8 parameters, nested objects, output schema), the description is remarkably complete. It explains the main workflow, costs, optional hi-res enhancement, and model routing. Because an output schema exists, the absence of return-value details is acceptable.

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 only 25%, so the description must compensate. It does add significant meaning for quality.hi_res_cells and quality.hi_res_model by explaining costs, purpose, and model routing, but it leaves most other core parameters (character, style, sheet, cells, output, provider) to the schema. The schema's nested titles and defaults help, but the description only partially fills the gap.

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?

The description uses a specific verb ('Generate') plus resource ('visual-novel character sprite sheet') and enumerates the exact pipeline steps: crop, chroma-key removal, validation, and manifest output. It clearly distinguishes this tool from siblings like generate_character_video or generate_scene_frame by scoping it to VN sprite sheets.

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

Usage Guidelines4/5

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

The description gives clear context for when to use the tool: to produce a VN Creator-ready sprite sheet with fixed-grid cropping and background removal. It does not explicitly name alternatives or exclusion criteria, but the specificity and billing details make the intended use unambiguous.

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

All designforyou tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.