Skip to main content
Glama

Generate custom print

studio_generate

Generate a CUSTOM t-shirt print from a text prompt (AI, takes 2-10 min). SPENDS THE ACCOUNT OWNER'S STUDIO CREDITS: tell them the cost and their balance and get a yes BEFORE calling this — never spend silently, and never spend to 'try something' on your own initiative. Credits are earned (20 free on signup, 20 with every tee bought), so a wasted one is a real loss to them. Free exception: preserve=true prints their own image as-is and costs nothing. IMPORTANT: first call studio_options and ask the human to pick placement + product (and optionally background); do NOT silently use defaults. Args: prompt (design description), product? (one of ['kids_basic_tshirt_boy', 'kids_basic_tshirt_girl', 'kids_oversize_tshirt_boy', 'kids_oversize_tshirt_girl', 'mens_basic_tshirt', 'mens_oversize_tshirt', 'womens_basic_tshirt', 'womens_oversize_tshirt']), background? (t-shirt background, one of ['washed-beige', 'washed-black', 'washed-blue', 'washed-brown', 'washed-gray', 'washed-green', 'washed-orange', 'washed-pink', 'washed-red', 'washed-yellow', 'watercolor-beige', 'watercolor-blue', 'watercolor-sky']), placement? (print size/position, one of ['portrait_extended', 'square_center', 'chest_small']), model? (nb2 default | gpt-image-2 — both 1 credit, different styles), image_url? (https link to the user's OWN image — used as style/subject reference), preserve? (true = print the user's image exactly as-is, no AI redraw — kids' drawings, own art; FREE, no credits; requires image_url). Returns print_id — poll studio_status until done.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNoGeneration engine: nb2 (default) or gpt-image-2 — both 1 credit.
promptYesText description of the design to generate.
productNoStudio product base from studio_options (default mens_oversize_tshirt).
preserveNotrue = print the image exactly as-is, no AI redraw (free); requires image_url.
image_urlNohttps link to the user's OWN image, used as style/subject reference.
placementNoPrint size/position: portrait_extended (default), square_center or chest_small.
backgroundNoT-shirt background choice (see studio_options backgrounds).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNo
errorNoe.g. not enough Studio credits, daily limit reached, invalid product.
detailNo
statusNo
print_idNoGeneration id — poll studio_status with it.
tell_userNoSay this to the account owner — what was spent from their balance and what is left.
topup_urlNoWhere the user can buy credits (present on 'not enough credits').
cost_creditsNoCredits spent on this generation.
signup_bonusNo
balance_afterNoCredits left after this generation.
balance_beforeNo
studio_account_createdNoPresent when a Studio account was auto-created for the user.

TDQS

A4.9/5.0
Behavior5/5

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

Description extensively discloses behavior beyond annotations: credit expenditure, cost details, generation time, polling requirement, and the free preserve exception. Since annotations are minimal (readOnlyHint=false, etc.), this description carries the full burden and does so thoroughly.

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?

The description is long but every sentence earns its place. It's structured logically: what it does, cost warning, exception, required pre-step, then param clarifications. Slightly dense but appropriately so for a complex tool.

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 (7 params, cost implications, sequencing with studio_options, async generation), the description covers all necessary behavioral context. It explains return (print_id) via output schema? Actually no output schema is provided here, but description mentions 'Returns print_id — poll studio_status' which is valuable. No gaps identified.

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 100% (all 7 params described in schema), but the description adds crucial context: e.g., product and background options come from studio_options, preserve requires image_url, placement meanings. It also clarifies defaults (like product default 'mens_oversize_tshirt') and the cost model for model param.

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?

Purpose is perfectly clear: 'Generate a CUSTOM t-shirt print from a text prompt' with the AI generation aspect and time estimate stated up front. It distinguishes itself from siblings like studio_options (pick placement/product) and studio_status (poll results) by explicitly referring to those as separate steps.

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?

Extremely explicit: warns against spending credits without permission, requires calling studio_options first, and differentiates free preserve=true case. Also tells the agent to ask the human for choices rather than defaulting.

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.

TDQS

A3.9/5.0
Disambiguation4/5

Tools are mostly distinct; slight overlap exists between cart_update and set_cart_quantity (both modify cart lines), and between remove_promo and cart_remove (different domains). Other groups (studio, designer) are well-separated.

Naming Consistency5/5

Consistent use of verb_noun pattern for most tools, with noun prefixes (designer_, studio_) grouping related tools. No mixed conventions or obscure abbreviations.

Tool Count3/5

31 tools is high for a single server, covering shopping, studio, and designer domains. Some tools like cart_update and set_cart_quantity seem redundant, pushing count beyond optimal.

Completeness4/5

Core workflows (search, cart, checkout, generation, designer submission) are covered. Minor gaps: no edit/delete for designs or orders, and no tool to manage saved addresses beyond viewing.

Resources