Skip to main content
Glama

Dripod

Design on a product

pod_mockup
Read-onlyIdempotent

Put a print-on-demand design on a product mockup in one blank colour and get a PNG. The design is the product's whole print area (a shirt's front, a mug's side, a case's back). Give the design as design_url (a public https link) or design_base64 (PNG, JPEG or WebP, at most 10 MB; a transparent PNG works best). Call it once per product and colour.

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": {
      "product": "<product>"
    },
    "name": "pod_mockup"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNoThe square PNG's side in pixels (default 1024).
colourNoOne of the product's colours (list_products), like "Black". Leave it out for its first.
productYesThe product (list_products), like "crew-neck-t-shirt".
backgroundNo"transparent" for a cut-out PNG, or a colour like "#ffffff". Leave it out for a soft studio grey.
design_urlNoA public https link to the design (PNG, JPEG or WebP).
design_base64NoThe design itself, base64 (a data: URL is fine).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive, so the safety profile is covered. The description adds real behavioural context on top: a 10 MB cap, accepted formats (PNG/JPEG/WebP), that transparent PNG yields the best result, and that only one blank colour is rendered per call. It does not say what the response contains (URL vs base64 payload) or what happens on failure, which keeps it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three front-loaded sentences: what it produces first, then what the input means, then how often to call it. No filler, no restatement of the title, and the constraints (10 MB, formats) are packed into the same sentence as the input description.

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 six parameters, one required, and no output schema, the description does the heavy lifting on inputs and states the output type (PNG) and its square size options come from the schema. It is nearly complete; the remaining gap is the shape of the returned PNG (link, base64, or binary) and error behaviour, which an agent calling it would want to know.

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 coverage is 100%, so the baseline is 3, but the description adds meaning the schema lacks: the design must be a public https link or base64, the whole image becomes the print area (no placement parameters exist), and it clarifies the design_url vs design_base64 choice and image constraints. That is a genuine semantic layer beyond the field descriptions.

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?

Specific verb+resource+output: putting a print-on-demand design on a product mockup and getting a PNG, in one blank colour. It also defines the design's role (the product's whole print area, with shirt-front / mug-side examples), so an agent knows exactly what the artifact is. Clearly distinct from the only sibling, list_products, which is only referenced for lookup of product/colour values.

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?

"Call it once per product and colour" gives explicit invocation cadence, and the sentence about the design covering the whole print area implicitly rules out positioning/scaling use. It stops short of naming an alternative tool or stating exclusions (e.g. when not to mock up), so it is clear context without full when/when-not coverage.

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.