Skip to main content
Glama

Reimagine Design

reimagine

Transform a design into a new style as code with an inspiration dial to control faithfulness, optionally remix a second design, and generate up to three variations.

Instructions

Reimagine a design in a new style as code. Control how far it departs from the original with the inspiration dial (0 = faithful, 100 = wild), optionally remix with a second design, and get up to 3 variations.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "reimagine"
  }
}

Input Schema

NameRequiredDescriptionDefault
dialNoInspiration dial: 0 faithful ... 100 wild
specNoJSON spec from analyze_design for the source design
imageNoLocal file path or http(s) URL of the source design
styleNoTarget style. Presets: minimal, brutalist, glassmorphism, neumorphism, retro-futuristic, editorial, playful, luxury, dark-mode, high-contrast. Any custom description also works.minimal
formatNoOutput code formathtml
remix_withNoOptional second design (path or URL): take its mood and style, keep the first design's structure
variationsNoHow many distinct variations to generate

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the output form (code), the variation ceiling (up to 3), and the remix behavior of taking mood from a second design while keeping the first's structure. It does not state that a source (spec or image) must effectively be supplied even though zero parameters are required, nor anything about cost/latency of generating multiple variations.

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?

A single well-formed sentence that front-loads the core action and then walks through dial, remix, and variations in the order an agent would reason about them. Slightly dense, and the dial parenthetical partly duplicates the schema, but nothing is wasted.

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

Completeness3/5

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

For a 7-parameter tool with no required fields, no annotations, and no output schema, the description covers the main knobs but leaves open the practical prerequisite of providing spec or image and how the returned variations are delivered. Adequate but with real gaps an agent would hit at call time.

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 100%, so the schema already documents dial, style presets, format enum, remix_with, and variations. The description restates the dial semantics and remix intent but adds no format details, precedence rules (what happens if both spec and image are given), or constraints beyond the schema.

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

Purpose4/5

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

The description names a specific verb and resource -- 'Reimagine a design in a new style as code' -- and adds the differentiating scope (style transfer producing code). It does not explicitly contrast with close siblings such as recreate or analyze_design, so an agent must infer the distinction from the style-transfer framing.

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

Usage Guidelines3/5

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

Usage is implied through the inspiration dial ('0 = faithful, 100 = wild') and the optional remix, which hints at when this tool is appropriate versus a faithful recreation. However, it never states when not to use it, nor names an alternative like recreate for exact reproduction.

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