Skip to main content
Glama

Create design

create_design

Create a new design with our image model, fitted to the product (aspect ratio, transparent background for clothing). Use this instead of generating an image yourself: only designs from this tool can be printed. Takes about 45 seconds.

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

Input Schema

NameRequiredDescriptionDefault
textNoExact text on the design, only if the user wants text
productYesProduct reference
descriptionYesRich description of the image: subject, pose, style, colours, mood
real_subjectNoOnly for a real, existing building, monument, bridge, windmill, church or recognisable place the user names: its name and town, e.g. 'Poldertoren Emmeloord'. The engine looks up a photo of it and draws the real one. Not for the user's own house, pet or people: ask for a photo.
reference_photoNoDesign id of a photo the user uploaded that shows what the subject really looks like (their dog, their house, or a photo of the building)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / real_subject
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 120,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Only for a real, existing building, monument, bridge, windmill, church or recognisable place the user names: its name and town, e.g. 'Poldertoren Emmeloord'. The engine looks up a photo of it and draws the real one. Not for the user's own house, pet or people: ask for a photo.",
      +  "title": "Real Subject"
      +}
    • addedInput schema / properties / reference_photo
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Design id of a photo the user uploaded that shows what the subject really looks like (their dog, their house, or a photo of the building)",
      +  "title": "Reference Photo"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Adds real context beyond the annotations: the ~45 second latency, the fact that output is auto-fitted to the product aspect ratio, and that only these designs are printable. That materially shapes agent expectations for a non-idempotent, non-read-only call. It does not mention cost/credits or what happens on repeated calls, so it is strong but not exhaustive.

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 short sentences with zero filler: purpose and product-fitting first, the differentiator second, latency last. Every sentence earns its place.

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?

There is no output schema, and the description never says what comes back — presumably a design id, which the agent would need to chain into edit_design, restyle_design or place_order (the reference_photo parameter hints designs have ids). Everything else needed to call it correctly is covered.

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%, and the parameter descriptions (notably real_subject and reference_photo) are richer than anything the tool description says. The description only echoes the product-fitting behavior. Baseline 3 is appropriate since the schema, not the description, carries parameter meaning.

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?

States a specific verb and resource ('Create a new design') and immediately narrows the scope: it is generated by their image model and fitted to the product's aspect ratio, with transparent background for clothing. The sentence 'only designs from this tool can be printed' separates it cleanly from siblings like use_chat_image, use_example, and edit_design.

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?

'Use this instead of generating an image yourself: only designs from this tool can be printed' gives a clear directive and the reason behind it, which is exactly the routing decision an agent faces with use_chat_image and use_example present. It stops short of naming those siblings or stating when-not-to-use conditions (e.g. editing an existing design should go to edit_design/restyle_design).

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