Skip to main content
Glama

1211 - your picture on a shirt

by com.1211holding
OverviewDiscussionsAdmin

Put a picture on an item and get the link to buy it

create_design

Puts a picture (a public link, an upload id, an attached file or SVG markup) on an item and colour and returns the page where the person sees it, picks sizes and pays, with a picture of the result, how big each side prints, the price including US shipping, and any problems. With no picture, it returns the page where the person adds their own picture to the item. A shirt's front prints small on the left chest or big and centered; backs print large. No payment passes through this tool: the person pays on the returned page. Printing requires that the person owns the art or has permission to print it. Limit: 30 designs per address per hour.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
devNoA developer's id, used with markup_usd.
refNoThe name of the assistant or app, such as "claude".
svgNoSVG markup (lettering or simple shapes) with a viewBox; scripts and linked files are removed. Fonts available: Lato, DejaVu Sans, DejaVu Serif, Liberation Sans, Liberation Serif, Nimbus Sans, URW Gothic, URW Bookman, C059, P052, Z003, Noto Color Emoji.
fileNoA file the person attached, in the shape ChatGPT passes.
itemYesThe item to print on.
sideNoWhere it prints (default front).
sizeNoA size to start with on the page, such as "L".
colorNoOne of the item's colours; left out, its default.
frontNochest: small on the left chest (default). center: big and centered, on T-shirts, sweatshirts and hoodies.
titleNoA name for the design (80 characters).
uploadNoAn upload id, instead of image_url.
image_urlNoA public http(s) link to the picture.
markup_usdNoDollars a developer adds to each item; the buyer sees the full price.
back_image_urlNoA different picture for the back.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

The description goes well beyond annotations by disclosing that no payment passes through the tool, printing requires ownership or permission, there is a rate limit, and specific print placement rules (front chest vs. center, backs large). These are critical behavioral details for correct invocation.

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 front-loaded with the primary action and return value, then adds constraints. It is a bit long but every sentence provides useful context; no significant waste.

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 (14 parameters, nested objects, no output schema) and its open-world, non-read-only nature, the description covers all essential aspects: inputs (picture types), outputs (page with preview, dimensions, price), behavioral constraints (no payment, permission requirement, rate limit), and print-specific rules.

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%, so the schema already documents all 14 parameters thoroughly. The description adds some contextual meaning (e.g., SVG handling, print placement) but does not need to compensate for missing parameter documentation; baseline 3 is appropriate.

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 states a specific verb and resource ('puts a picture... on an item') and clearly explains what the tool returns (a preview/checkout page with print dimensions, price with US shipping, and issues). It is distinguishable from siblings like get_design or list_items by focusing on the creation flow.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains the core usage context (with or without a picture) and includes a key operational constraint (30 designs per address per hour). However, it does not explicitly state when to use create_design versus get_design or check_art, leaving some routing to inference.

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

All 1211 - your picture on a shirt toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources