Skip to main content
Glama

Pngtee: transparent PNG maker for shirts

Make a design

generate

Upload the shirt design you have, or describe one, and get a transparent PNG with no box behind the art, checked on a dark and a light shirt color. With a redeem code that has credits it spends one credit and returns the clean PNG's URL. Without a code it returns a free watermarked preview URL and an unlock object that says how your user can pay.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNoThe redeem code your user got after paying on the site. Optional when the MCP connection already sends it as Authorization: Bearer.
presetNoThe style. Defaults to the first.
promptNoWhat the image shows, 3 to 400 characters. One subject works best. No real people. Give this OR image_url.
image_urlNoAn https URL of an existing design (PNG, JPG or WebP, up to 24 MB). Its background is removed and its edge cleaned; nothing is redrawn.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false; the description adds the material facts those omit — that a call consumes one credit, that the unauthenticated path returns a watermarked preview rather than the real asset, and that a supplied image_url is background-removed and never redrawn. Cost and free-tier degradation are exactly the behaviors an agent needs before deciding to invoke.

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?

Two sentences, front-loaded with the outcome and then the paid versus free paths; every clause carries information. The second sentence is a long run-on that stacks credit spend, URL return, watermark and unlock object, which slightly hurts scannability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 steps in to describe return values: the clean PNG URL, or a preview URL plus an unlock object explaining how the user pays. All four parameters are documented in the schema. Minor gaps remain: it does not say what happens when a code has no credits left, nor whether retrying after a failure charges again.

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 prompt, image_url, preset and code are already described, including the 'give this OR image_url' rule and the 24 MB / 3-400 character limits. The description adds only slight meaning, notably that the code must actually hold credits and that image_url is not regenerated, so the baseline of 3 is warranted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete verb+resource: turn an uploaded design or a text prompt into a background-free transparent PNG, verified against dark and light shirt colors. It is clear and specific enough that an agent knows what the tool produces, but it never distinguishes this tool from the sibling tools (balance, redeem_info), so differentiation is left to inference.

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 clearly splits the two usage paths: with a redeem code holding credits (charged) versus without a code (free watermarked preview plus an unlock object). What is missing is guidance tying it to the siblings — it says a code 'has credits' but never directs the agent to check with balance or to redeem_info before calling.

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