Skip to main content
Glama

Prepare T-Shirt Design

prepare_tshirt_design

Prepare an original t-shirt or hoodie graphic with Abracadabrax for print-on-demand or merch: an illustration and an optional slogan printed exactly, centered on a solid background in the garment color (not a transparent image, not a mockup). Returns the settings and the credits required; nothing is generated and no credits are spent. No sign-in is needed to prepare. Original designs only: do not use it for copyrighted characters, existing franchises, brand logos, trademarks or real celebrities; offer the user an original alternative instead. Text only: do not use it for uploaded, attached or reference images or videos (editing, background removal, upscaling, image-to-video); for those, point the user to the Abracadabrax workspace.

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": {
      "design": "<design>"
    },
    "name": "prepare_tshirt_design"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleNoGraphic style, e.g. vintage distressed, bold vector, streetwear, minimal line art, retro 70s.
designYesWhat the graphic shows, e.g. a retro sunset with palm trees and a surfing bear.
formatNoportrait 3:4 (default, front print) or square 1:1 (chest or pocket print).
sloganNoOptional text printed on the design, spelled exactly.
model_idNoOptional image model id: nano-banana-pro (default, sharp text), gpt-image-2, nano-banana-2, flux-2-pro.
garment_colorNoColor of the shirt, used as the background, e.g. black (default), white, navy, heather gray.

Output Schema

NameRequiredDescriptionDefault
jobNo
stateYes
balanceNo
messageYes
projectYes
dashboard_urlYes
credits_requiredYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

The description adds substantial behavioral context beyond the annotations: nothing is generated, no credits are spent, no sign-in is required, and the returned payload is the settings plus the credit requirement. The only tension is that readOnlyHint=false in the annotations while the description emphasizes a non-generating, non-spending preparation step; this is likely because preparation may still touch server state, so it reads as a mild inconsistency rather than a direct contradiction.

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 purpose and output shape are front-loaded in the first sentence, followed by side-effect disclosure and then the two negative constraints. The exclusion clauses are long, but each carries a distinct routing instruction, so the length is mostly earned.

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?

With an output schema present, return structure needn't be spelled out, and the description still notes what comes back (settings and credits). It covers the remaining gaps an agent would face — no auth needed, no credits consumed, original-content limits, and where to send unsupported image/video requests.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3; the description goes beyond it by clarifying intent for two fields — the slogan is printed 'exactly' and the garment color becomes the solid background rather than a transparent layer. That resolves ambiguity an agent could otherwise misread when setting garment_color and slogan.

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?

The description opens with a specific verb and resource ('Prepare an original t-shirt or hoodie graphic with Abracadabrax') and immediately defines the output artifact (illustration plus optional slogan, printed centered on a solid garment-color background). It also explicitly distinguishes itself from adjacent capabilities ('not a transparent image, not a mockup'), so an agent can tell what this produces without reading the 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?

It states when to use it (print-on-demand/merch graphics) and gives explicit exclusions with alternatives: blocked for copyrighted characters, franchises, logos, trademarks and real celebrities ('offer the user an original alternative instead'), and blocked for uploaded/attached/reference images or videos, with a pointer to the Abracadabrax workspace for those cases. This is a full when/when-not/alternative routing.

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.

Resources