Skip to main content
Glama

Start designing a photo frame

start_frame

Start designing a new photo frame for this operator's booths from a description of the look they want — 'batik motifs in warm gold', 'minimal Scandinavian, lots of white space'. It opens a design thread and makes the FIRST version. It returns immediately with a job id; call check_generation to see the result, and do NOT describe the frame as made until that says so. The result is a preview in the thread — nothing is in the operator's frame list until save_frame is called with the generation they choose. To change a result, call refine_frame with the threadId that check_generation returns, rather than starting again. Every generation spends part of the account's free daily allowance, so do not call this speculatively, twice for the same request, or while another generation is still running.

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": {
      "prompt": "<prompt>",
      "layout": "<layout>"
    },
    "name": "start_frame"
  }
}

Input Schema

NameRequiredDescriptionDefault
shapeNoThe shape the photos are cut to. Defaults to rectangular. Not every layout comes in every shape; the Studio picks the closest available.
layoutYesHow many photos and how they sit. 'strip-3': the classic photo strip — 3 photos stacked, printed as a pair on a 4x6; 'strip-4': a taller strip — 4 photos stacked, printed as a pair on a 4x6; 'grid-4': 4 photos in a 2x2 grid on one 4x6; 'hero-3': one large photo with two smaller ones beneath it; 'pair-2': two landscape photos, one above the other. Ask if it is not obvious from what the operator said; 'strip-3' is what most people mean by a photobooth strip.
promptYesWhat the frame should look like: decoration, colour, occasion. Not the photo slots — those come from the layout. Start with what the operator asked for, in their words and language, written as a description rather than a request: drop the wrapper ('design me a', 'make me', 'can you', 'buatkan', 'bikinin', 'tolong') and do not put it in quotation marks — the Studio prints quoted words as they are. Then add the brief. Never swap a choice they made for one you prefer; fill only what they left open. Write it as a designer's brief, not a caption. Keep their specifics exactly (names, colours, motif names such as kawung or mega mendung, the occasion) and make concrete: one technique (e.g. risograph, linocut, screen print, paper cut-out, gouache, batik tulis); 2-3 colours, named or hex; 1-3 named motifs and where they sit (top band, corners, along the edge); how dense it is — a plain paper colour or texture around the photos is a valid choice, say which. Add nothing they did not ask for: no sparkles, glitter, bokeh, lens flare, glow, glossy 3D, no praise words ('stunning', 'elegant', 'magical', 'vibrant', 'intricate', 'high quality', '4k'). If it is too vague to fill these in, ask one question, or pick one direction and tell the operator which. Do not name brands, characters or franchises; the image model refuses them.

Output Schema

NameRequiredDescriptionDefault
kindYes
noteNo
whatYes
errorNo
jobIdYes
stateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / prompt / description
      Previous value: -"What the frame should look like: decoration, colour, occasion. Not the photo slots — those come from the layout. Start with what the operator said, in their words and language, then add the brief. Never swap a choice they made for one you prefer; fill only what they left open. Write it as a designer's brief, not a caption. Keep their specifics exactly (names, colours, motif names such as kawung or mega mendung, the occasion) and make concrete: one technique (e.g. risograph, linocut, screen print, paper cut-out, gouache, batik tulis); 2-3 colours, named or hex; 1-3 named motifs and where they sit (top band, corners, along the edge); how dense it is — a plain paper colour or texture around the photos is a valid choice, say which. Add nothing they did not ask for: no sparkles, glitter, bokeh, lens flare, glow, glossy 3D, no praise words ('stunning', 'elegant', 'magical', 'vibrant', 'intricate', 'high quality', '4k'). If it is too vague to fill these in, ask one question, or pick one direction and tell the operator which. Do not name brands, characters or franchises; the image model refuses them."New value: +"What the frame should look like: decoration, colour, occasion. Not the photo slots — those come from the layout. Start with what the operator asked for, in their words and language, written as a description rather than a request: drop the wrapper ('design me a', 'make me', 'can you', 'buatkan', 'bikinin', 'tolong') and do not put it in quotation marks — the Studio prints quoted words as they are. Then add the brief. Never swap a choice they made for one you prefer; fill only what they left open. Write it as a designer's brief, not a caption. Keep their specifics exactly (names, colours, motif names such as kawung or mega mendung, the occasion) and make concrete: one technique (e.g. risograph, linocut, screen print, paper cut-out, gouache, batik tulis); 2-3 colours, named or hex; 1-3 named motifs and where they sit (top band, corners, along the edge); how dense it is — a plain paper colour or texture around the photos is a valid choice, say which. Add nothing they did not ask for: no sparkles, glitter, bokeh, lens flare, glow, glossy 3D, no praise words ('stunning', 'elegant', 'magical', 'vibrant', 'intricate', 'high quality', '4k'). If it is too vague to fill these in, ask one question, or pick one direction and tell the operator which. Do not name brands, characters or franchises; the image model refuses them."
  2. Changed1 schema field changed
    • changedInput schema / properties / prompt / description
      Previous value: -"What the frame should look like: decoration, colour, occasion. Not the photo slots — those come from the layout. Write a designer's brief, not a caption. Keep the operator's specifics exactly (names, colours, motif names such as kawung or mega mendung, the occasion) and make concrete: one technique (e.g. risograph, linocut, screen print, paper cut-out, gouache, batik tulis); 2-3 colours, named or hex; 1-3 named motifs and where they sit (top band, corners, along the edge); how dense it is — a plain paper colour or texture around the photos is a valid choice, say which. Add nothing they did not ask for: no sparkles, glitter, bokeh, lens flare, glow, glossy 3D, no praise words ('stunning', 'elegant', 'magical', 'vibrant', 'intricate', 'high quality', '4k'). If it is too vague to fill these in, ask one question, or pick one direction and tell the operator which. Do not name brands, characters or franchises; the image model refuses them."New value: +"What the frame should look like: decoration, colour, occasion. Not the photo slots — those come from the layout. Start with what the operator said, in their words and language, then add the brief. Never swap a choice they made for one you prefer; fill only what they left open. Write it as a designer's brief, not a caption. Keep their specifics exactly (names, colours, motif names such as kawung or mega mendung, the occasion) and make concrete: one technique (e.g. risograph, linocut, screen print, paper cut-out, gouache, batik tulis); 2-3 colours, named or hex; 1-3 named motifs and where they sit (top band, corners, along the edge); how dense it is — a plain paper colour or texture around the photos is a valid choice, say which. Add nothing they did not ask for: no sparkles, glitter, bokeh, lens flare, glow, glossy 3D, no praise words ('stunning', 'elegant', 'magical', 'vibrant', 'intricate', 'high quality', '4k'). If it is too vague to fill these in, ask one question, or pick one direction and tell the operator which. Do not name brands, characters or franchises; the image model refuses them."
  3. Changed1 schema field changed
    • changedInput schema / properties / prompt / description
      Previous value: -"What the frame should look like, in the operator's own words where possible: decoration, colour, mood, occasion. Not the photo slots — those come from the layout. Do not name brands, characters or franchises; the image model refuses them."New value: +"What the frame should look like: decoration, colour, occasion. Not the photo slots — those come from the layout. Write a designer's brief, not a caption. Keep the operator's specifics exactly (names, colours, motif names such as kawung or mega mendung, the occasion) and make concrete: one technique (e.g. risograph, linocut, screen print, paper cut-out, gouache, batik tulis); 2-3 colours, named or hex; 1-3 named motifs and where they sit (top band, corners, along the edge); how dense it is — a plain paper colour or texture around the photos is a valid choice, say which. Add nothing they did not ask for: no sparkles, glitter, bokeh, lens flare, glow, glossy 3D, no praise words ('stunning', 'elegant', 'magical', 'vibrant', 'intricate', 'high quality', '4k'). If it is too vague to fill these in, ask one question, or pick one direction and tell the operator which. Do not name brands, characters or franchises; the image model refuses them."
  4. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare it as a non-read-only, non-idempotent, non-destructive open-world mutation; the description goes well beyond that by disclosing the async job-id return, the instruction to wait for check_generation before claiming completion, that nothing enters the frame list until save_frame, and that each call consumes the free daily allowance. The remaining gap is retry/failure behavior or what a failed generation costs the allowance.

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?

Front-loaded with purpose, then the async contract, then the not-yet-saved caveat, then the cost warning — a sensible order. It is a dense block of five long sentences; the refine_frame pointer could be folded into the async sentence, but nearly every clause carries actionable information.

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?

For an async, credit-consuming creation tool with an output schema, the description covers the full lifecycle: job id returned immediately, result checked elsewhere, preview versus saved state, the refine path, and the cost constraint. An agent has everything needed to call it correctly and to avoid the common failure of announcing a frame that does not exist yet.

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 prompt, layout, and shape are already richly documented — the schema's prompt guidance is in fact more detailed than the description's. The description only echoes the prompt concept with two example phrases, adding no new syntax or constraint beyond the schema, so baseline 3 applies.

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 — 'Start designing a new photo frame' — and pins the scope to 'this operator's booths' from a text description. It also implicitly separates itself from refine_frame, save_frame, and check_generation by describing the new-thread creation role, so an agent can place it in the workflow 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?

Gives explicit when-to-use (a new design from a look description), when-not-to (not speculatively, not twice for the same request, not while another generation runs), and names the alternative for modification: 'To change a result, call refine_frame ... rather than starting again.' That is a complete routing rule set.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.