Skip to main content
Glama

Design a new booth

start_booth

Design a complete photobooth (a 'booth') for this operator from a description — the Studio designs the welcome screen for phone and laptop, the in-booth background, the colour theme, the capture mode, a title and a link name, exactly as dreambooth.app/new does. Before calling, gather in chat what /new would ask and put ALL of it in the prompt: the occasion or business, the vibe or style, colours, and the language the booth should speak — there is no separate questions step. It returns a job id immediately; call check_generation, and do NOT describe the booth as designed or created until that says done. The result is a DRAFT with a draftId: nothing is in the operator's booth list until create_booth. Every call makes a new draft and spends 1 of its 3 full generations, and an account may start 10 drafts an hour — never call it speculatively or twice for one request; change a draft with refine_booth instead.

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>"
    },
    "name": "start_booth"
  }
}

Input Schema

NameRequiredDescriptionDefault
promptYesThe booth, from what the operator said and what you gathered, up to 1000 characters. 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. Do not name brands, characters or franchises; the image model refuses them.
languageNoThe language the booth's own text should be in, as a code: 'id', 'en', 'es'. Defaults to English — ask if the operator's booth is not in English.

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: -"The booth, from what the operator said and what you gathered, up to 1000 characters. 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. Do not name brands, characters or franchises; the image model refuses them."New value: +"The booth, from what the operator said and what you gathered, up to 1000 characters. 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. Do not name brands, characters or franchises; the image model refuses them."
  2. Changed1 schema field changed
    • changedInput schema / properties / prompt / description
      Previous value: -"The booth, from what the operator said and what you gathered, up to 1000 characters. 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. Do not name brands, characters or franchises; the image model refuses them."New value: +"The booth, from what the operator said and what you gathered, up to 1000 characters. 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. Do not name brands, characters or franchises; the image model refuses them."
  3. Changed1 schema field changed
    • changedInput schema / properties / prompt / description
      Previous value: -"The booth, in the operator's words plus what you gathered: occasion or business, vibe and style, colours, mood, anything that must appear. Up to 1000 characters. Do not name brands, characters or franchises; the image model refuses them."New value: +"The booth, from what the operator said and what you gathered, up to 1000 characters. 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. Do not name brands, characters or franchises; the image model refuses them."
  4. Added

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: the call is asynchronous and returns a job id immediately, nothing is 'done' until check_generation says so, the result is a DRAFT keyed by draftId that is invisible in the operator's booth list until create_booth. It also discloses cost and rate limits — 1 of 3 full generations spent per call, 10 drafts per hour per account — which no annotation conveys.

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?

Purpose and preconditions are front-loaded, and most clauses carry operational weight (cost, rate limit, draft state, alternatives). However, it is a single dense paragraph mixing what-it-does, pre-call prep, polling, lifecycle and cost, and it repeats prompt-writing rules already present in the schema (no emoji, no praise words), making it harder to scan than it needs to be.

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 a costly, asynchronous, non-idempotent generation tool with an output schema, the description covers everything an agent needs before invoking: required input gathering, the async contract, the polling step, the draft lifecycle, spend and rate limits, and the sibling to use for edits. Nothing material is left for inference.

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 coverage is 100% and the prompt parameter's schema description is already exhaustive, so the description's guidance (gather occasion, vibe, colours, language into the prompt) largely restates it at summary level. It adds one useful framing — there is no separate questions step, so everything must go in one prompt — but no syntax or format detail beyond the schema. 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 ('Design a complete photobooth (a booth) for this operator from a description') and enumerates what is produced: welcome screen, in-booth background, colour theme, capture mode, title, link name. It also implicitly distinguishes itself from create_booth, refine_booth and start_frame by declaring the output is a draft generation job rather than a listed booth or a frame.

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?

Explicit preconditions ('Before calling, gather in chat what /new would ask and put ALL of it in the prompt'), explicit follow-up ('call check_generation'), explicit prohibition ('never call it speculatively or twice for one request'), and an explicit alternative for edits ('change a draft with refine_booth instead'). The agent is told when to use, when not to use, and which sibling to use instead.

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.