Skip to main content
Glama

Refine a booth draft

refine_booth
Destructive

Change a booth draft from start_booth, using the draftId check_generation returned. what='welcome' redraws the welcome screen from an instruction ('warmer colours', 'bigger headline', 'less clutter') while keeping the design; add orientation 'phone' or 'laptop' to redraw only that screen (1 redraw) — without it both screens are redrawn (2). To change the words on the welcome screen (the couple's names, a new headline), pass headline with the exact new words: it is stored on the draft and both screens are repainted with it (2 redraws). Never use orientation for that, or the phone and laptop screens say different things. what='app-background' redraws the calmer backdrop behind the rest of the booth (1 redraw). what='everything' rebuilds the whole draft from a NEW full description (spends 1 of the draft's 3 full generations) — only when the operator wants a different booth, not a tweak. A draft has 5 redraws in total; check_generation reports what is left. Title, headline, link name and colours cannot be edited directly: they change only through a redraw instruction, or at create time (title, slug). Returns a job id; call check_generation. Call only when the operator asks for a change — never iterate on your own.

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": {
      "draftId": "<draftId>",
      "what": "<what>",
      "instruction": "<instruction>"
    },
    "name": "refine_booth"
  }
}

Input Schema

NameRequiredDescriptionDefault
whatYesWhich part to change. 'everything' is a full rebuild from a new description.
draftIdYesThe draft to change, from check_generation's result for start_booth.
headlineNoOnly with what='welcome': the new welcome headline exactly as it should read, in the booth's language (e.g. 'Sania & Senya'). Both screens are redrawn with it.
instructionYesFor 'welcome' / 'app-background': what to change, up to 300 characters — the current design is kept and only this is applied. State the change and nothing else, starting from the operator's own words: what changes, to what, and what to keep if that matters ('background to deep green #1F3B2D, keep the motifs where they are'). Turn a vague word into a concrete change ('more festive' → which colour, motif or density moves). Do not restate the original design or add mood or praise words. For 'everything': the new full description of the booth, up to 1000 characters, written the way start_booth's prompt is: 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 facts and art direction, not marketing copy. Include: the occasion or business, with names, ages, dates and places exactly as given; one visual reference in words — theirs if they gave one, otherwise one you pick from the occasion and name to them (e.g. '1970s Indonesian film poster', 'hand-painted warung sign', 'Swiss minimalist poster'); do not ask them for one; 2-3 colours; 2-4 concrete objects or motifs (e.g. 'enamel tin mugs', 'pressed jasmine'). Do not write the headline or taglines — the Studio writes the copy — unless the operator gave exact wording to print; then quote only that wording and say it must appear as written. Quotation marks are for nothing else. No emoji, no praise words ('stunning', 'elegant', 'magical', 'vibrant', 'intricate', 'high quality', '4k', 'unforgettable'), no sparkles, glitter, bokeh, lens flare, glow, glossy 3D unless asked.
orientationNoOnly with what='welcome': redraw just the phone (portrait) or laptop (landscape) screen. Omit to redraw both. Never with headline.

Output Schema

NameRequiredDescriptionDefault
kindYes
noteNo
whatYes
errorNo
jobIdYes
stateYes
draftIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / headline
      Added value: +{
      +  "description": "Only with what='welcome': the new welcome headline exactly as it should read, in the booth's language (e.g. 'Sania & Senya'). Both screens are redrawn with it.",
      +  "maxLength": 60,
      +  "minLength": 2,
      +  "type": "string"
      +}
    • changedInput schema / properties / orientation / description
      Previous value: -"Only with what='welcome': redraw just the phone (portrait) or laptop (landscape) screen. Omit to redraw both."New value: +"Only with what='welcome': redraw just the phone (portrait) or laptop (landscape) screen. Omit to redraw both. Never with headline."
  2. Changed1 schema field changed
    • changedInput schema / properties / instruction / description
      Previous value: -"For 'welcome' / 'app-background': what to change, up to 300 characters — the current design is kept and only this is applied. State the change and nothing else, starting from the operator's own words: what changes, to what, and what to keep if that matters ('background to deep green #1F3B2D, keep the motifs where they are'). Turn a vague word into a concrete change ('more festive' → which colour, motif or density moves). Do not restate the original design or add mood or praise words. For 'everything': the new full description of the booth, up to 1000 characters, written the way start_booth's prompt is: 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 facts and art direction, not marketing copy. Include: the occasion or business, with names, ages, dates and places exactly as given; one visual reference in words — theirs if they gave one, otherwise one you pick from the occasion and name to them (e.g. '1970s Indonesian film poster', 'hand-painted warung sign', 'Swiss minimalist poster'); do not ask them for one; 2-3 colours; 2-4 concrete objects or motifs (e.g. 'enamel tin mugs', 'pressed jasmine'). Do not write the headline or taglines — the Studio writes the copy — unless the operator gave exact wording; then quote it and say it must appear as written. No emoji, no praise words ('stunning', 'elegant', 'magical', 'vibrant', 'intricate', 'high quality', '4k', 'unforgettable'), no sparkles, glitter, bokeh, lens flare, glow, glossy 3D unless asked."New value: +"For 'welcome' / 'app-background': what to change, up to 300 characters — the current design is kept and only this is applied. State the change and nothing else, starting from the operator's own words: what changes, to what, and what to keep if that matters ('background to deep green #1F3B2D, keep the motifs where they are'). Turn a vague word into a concrete change ('more festive' → which colour, motif or density moves). Do not restate the original design or add mood or praise words. For 'everything': the new full description of the booth, up to 1000 characters, written the way start_booth's prompt is: 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 facts and art direction, not marketing copy. Include: the occasion or business, with names, ages, dates and places exactly as given; one visual reference in words — theirs if they gave one, otherwise one you pick from the occasion and name to them (e.g. '1970s Indonesian film poster', 'hand-painted warung sign', 'Swiss minimalist poster'); do not ask them for one; 2-3 colours; 2-4 concrete objects or motifs (e.g. 'enamel tin mugs', 'pressed jasmine'). Do not write the headline or taglines — the Studio writes the copy — unless the operator gave exact wording to print; then quote only that wording and say it must appear as written. Quotation marks are for nothing else. No emoji, no praise words ('stunning', 'elegant', 'magical', 'vibrant', 'intricate', 'high quality', '4k', 'unforgettable'), no sparkles, glitter, bokeh, lens flare, glow, glossy 3D unless asked."
  3. Changed1 schema field changed
    • changedInput schema / properties / instruction / description
      Previous value: -"For 'welcome' / 'app-background': what to change, up to 300 characters — the current design is kept and only this is applied. State the change and nothing else: what changes, to what, and what to keep if that matters ('background to deep green #1F3B2D, keep the motifs where they are'). Turn a vague word into a concrete change ('more festive' → which colour, motif or density moves). Do not restate the original design or add mood or praise words. For 'everything': the new full description of the booth, up to 1000 characters, written the way start_booth's prompt is: Write facts and art direction, not marketing copy. Include: the occasion or business, with names, ages, dates and places exactly as given; one concrete visual reference (e.g. '1970s Indonesian film poster', 'hand-painted warung sign', 'Swiss minimalist poster'); 2-3 colours; 2-4 concrete objects or motifs (e.g. 'enamel tin mugs', 'pressed jasmine'). Do not write the headline or taglines — the Studio writes the copy — unless the operator gave exact wording; then quote it and say it must appear as written. No emoji, no praise words ('stunning', 'elegant', 'magical', 'vibrant', 'intricate', 'high quality', '4k', 'unforgettable'), no sparkles, glitter, bokeh, lens flare, glow, glossy 3D unless asked."New value: +"For 'welcome' / 'app-background': what to change, up to 300 characters — the current design is kept and only this is applied. State the change and nothing else, starting from the operator's own words: what changes, to what, and what to keep if that matters ('background to deep green #1F3B2D, keep the motifs where they are'). Turn a vague word into a concrete change ('more festive' → which colour, motif or density moves). Do not restate the original design or add mood or praise words. For 'everything': the new full description of the booth, up to 1000 characters, written the way start_booth's prompt is: 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 facts and art direction, not marketing copy. Include: the occasion or business, with names, ages, dates and places exactly as given; one visual reference in words — theirs if they gave one, otherwise one you pick from the occasion and name to them (e.g. '1970s Indonesian film poster', 'hand-painted warung sign', 'Swiss minimalist poster'); do not ask them for one; 2-3 colours; 2-4 concrete objects or motifs (e.g. 'enamel tin mugs', 'pressed jasmine'). Do not write the headline or taglines — the Studio writes the copy — unless the operator gave exact wording; then quote it and say it must appear as written. No emoji, no praise words ('stunning', 'elegant', 'magical', 'vibrant', 'intricate', 'high quality', '4k', 'unforgettable'), no sparkles, glitter, bokeh, lens flare, glow, glossy 3D unless asked."
  4. Changed1 schema field changed
    • changedInput schema / properties / instruction / description
      Previous value: -"For 'welcome' / 'app-background': what to change, in the operator's words, up to 300 characters — the current design is kept and only this is applied. For 'everything': the new full description of the booth, up to 1000 characters."New value: +"For 'welcome' / 'app-background': what to change, up to 300 characters — the current design is kept and only this is applied. State the change and nothing else: what changes, to what, and what to keep if that matters ('background to deep green #1F3B2D, keep the motifs where they are'). Turn a vague word into a concrete change ('more festive' → which colour, motif or density moves). Do not restate the original design or add mood or praise words. For 'everything': the new full description of the booth, up to 1000 characters, written the way start_booth's prompt is: Write facts and art direction, not marketing copy. Include: the occasion or business, with names, ages, dates and places exactly as given; one concrete visual reference (e.g. '1970s Indonesian film poster', 'hand-painted warung sign', 'Swiss minimalist poster'); 2-3 colours; 2-4 concrete objects or motifs (e.g. 'enamel tin mugs', 'pressed jasmine'). Do not write the headline or taglines — the Studio writes the copy — unless the operator gave exact wording; then quote it and say it must appear as written. No emoji, no praise words ('stunning', 'elegant', 'magical', 'vibrant', 'intricate', 'high quality', '4k', 'unforgettable'), no sparkles, glitter, bokeh, lens flare, glow, glossy 3D unless asked."
  5. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare destructive/openWorld/non-idempotent; the description adds the budget model (5 redraws total, 3 full generations, 1 vs 2 redraws per mode), the fact that it returns a job id rather than the result, and that certain fields (title, headline, link name, colours) cannot be edited directly. That is exactly the context beyond annotations an agent needs before spending a limited resource.

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

Conciseness3/5

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

Front-loaded and logically ordered (draftId source, then each 'what' mode, then constraints), but the long instruction-authoring paragraph largely restates the instruction parameter's schema description verbatim, so a chunk of the text does not add value beyond structured fields. Dense run-on sentences with parenthetical redraw costs make it slower to parse than necessary.

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?

Covers input provenance, per-mode cost, prohibited parameter combinations, non-editable fields, the returned job id, and the follow-up tool. An output schema exists, so the description correctly does not spend words on return shape beyond the job id.

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

Parameters5/5

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

Schema coverage is already 100%, yet the description adds real meaning the schema cannot express: the redraw cost of each 'what' value, the interaction rule that orientation must never accompany headline, and the distinction between changing the welcome copy versus redrawing it. The instruction-writing guidance is extensive and operational.

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?

Opens with a specific verb+resource (change a booth draft), names the sibling that produced the input (start_booth) and the one that supplies draftId (check_generation). The three modes of 'what' are each given a concrete effect, so an agent can distinguish this tool from start_booth, refine_frame, and update_booth_draft 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?

Explicitly routes: 'everything' only when the operator wants a different booth, not a tweak; orientation only for a single-screen redraw and never with headline; call only when the operator asks, never iterate on your own. Also names check_generation as the follow-up step and the budget check.

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.