Skip to main content
Glama
Sign In

lookunique

by io.github.chemic
OverviewDiscussionsAdmin

Print words on a shirt

print_words

Sets the person’s own words as lettering on a t-shirt — a name, a phrase, a team, a date — in one to three lines of up to 48 characters. Returns eight styles at once (an arch, a round seal, handwritten, stacked type, a typed label…), only their words, the shop’s dots as the ornament. Given after — a drawing_id it returned — it returns eight more styles for the same words. Given photo — the design_id of a drawn picture, made from a photo or from the person’s words — it sets the words with that picture (light shirts only).

Input Schema

NameRequiredDescriptionDefault
afterNoA drawing_id from print_words: eight more styles for the same words (lines are then not needed).
linesNoOne to three lines of text, as they should read.
photoNoThe design_id of a drawn picture, from a photo or from words: the words are set with that picture — on light shirts only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / photo / description
      Previous value: -"A design_id of a picture drawn from a photo: the words are set with that picture — on light shirts only."New value: +"The design_id of a drawn picture, from a photo or from words: the words are set with that picture — on light shirts only."
    • changedInput schema / properties / photo / pattern
      Previous value: -"^custom-[0-9a-f]{8}/photo-\\d{1,2}$"New value: +"^custom-[0-9a-f]{8}/(photo|tone)-\\d{1,2}$"
  2. Changed1 schema field changed
    • addedInput schema / properties / photo
      Added value: +{
+  "description": "A design_id of a picture drawn from a photo: the words are set with that picture — on light shirts only.",
+  "pattern": "^custom-[0-9a-f]{8}/photo-\\d{1,2}$",
+  "type": "string"
+}
  3. Changed2 schema fields changed
    • addedInput schema / properties / after
      Added value: +{
+  "description": "A drawing_id from print_words: eight more styles for the same words (lines are then not needed).",
+  "pattern": "^custom-[0-9a-f]{8}$",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "lines"
-]
  4. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The description adds meaningful behavior beyond annotations: it returns eight styles at once, renders only the person's words with the shop's dots as ornament, and clarifies that `after` produces eight more styles. Annotations already declare it is non-destructive and non-idempotent, and the description's 'sets... as lettering' is consistent with a write operation. It does not disclose permissions or rate-limit behavior, but this is not expected given the context.

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 core action and then explains the two optional modes. It is efficient and largely free of filler, though the parenthetical list of styles is slightly verbose for the amount of decision-relevant information it conveys.

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 no output schema, the description carries the burden of explaining what is returned, and it does so adequately: eight styles containing only the words, plus the ability to paginate more styles via `after`. The conditional `photo` behavior and the light-shirts-only restriction are also made explicit.

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 description coverage is 100%, so the schema already documents all three parameters in detail, including the `after` pattern and the `photo` pattern. The description repeats much of that meaning (e.g., `after` as a returned drawing_id, `photo` for light shirts only) but adds little syntax or format detail beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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: it sets the person's own words as lettering on a t-shirt, returning eight styles at once. It clearly distinguishes this from siblings like draw_shirt by centering on user-supplied text and style generation, not on drawing a shirt.

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 mode-switching logic precisely: pass `after` to get eight more styles for the same words, pass `photo` to combine words with a drawn picture (light shirts only). It does not explicitly name when to prefer a sibling tool, so it falls just short of a 5.

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

All lookunique 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