Skip to main content
Glama

WELANDA Engraving Designer

Create design draft

create_design

Create a design draft for a product from a DesignDocumentV3. Returns status "valid" with a signed handoffUrl, or status "invalid" with a list of {path, code, message} errors you can fix and resubmit via update_design. Invalid drafts are still saved so you can iterate.

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": {
      "productRef": "<productRef>",
      "design": "<design>"
    },
    "name": "create_design"
  }
}

Input Schema

NameRequiredDescriptionDefault
designYesA DesignDocumentV3 (mm-native). templateId/templateVersion are set by the service. Shape and limits come from list_personalizable_products.
productRefYesA productRef from list_personalizable_products (e.g. "welanda-can-60-black").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / design / additionalProperties
      Added value: +{}
    • changedInput schema / properties / design / description
      Previous value: -"A DesignDocumentV3 (mm-native). templateId/templateVersion are set by the service."New value: +"A DesignDocumentV3 (mm-native). templateId/templateVersion are set by the service. Shape and limits come from list_personalizable_products."
    • addedInput schema / properties / design / properties
      Added value: +{}
    • addedInput schema / properties / design / type
      Added value: +"object"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Goes well beyond the annotations, which only mark this as a non-idempotent, non-destructive write. It discloses the persisted side effect (invalid drafts are still saved), the response discriminator, and the handoffUrl on success — exactly the kind of behavior an agent can't infer from annotations alone.

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 tight sentences: the action first, then the success/failure contract, then the iteration note. No redundant restatement of the title or schema.

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?

For a two-param, nested-object tool with no output schema, the description covers both branches of the return, the saved-on-invalid side effect, and where the document shape is defined. An agent has everything needed to call it and handle the response.

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% and the schema already explains productRef's origin and the DesignDocumentV3 template handling, so the description adds little parameter-level meaning. Baseline 3 applies since the structured fields do the work.

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 design draft for a product") and pins down the input type (DesignDocumentV3). It also enumerates the two possible outcomes, so an agent knows the tool's shape without opening the schema.

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?

Explicitly routes a failed attempt to update_design ("fix and resubmit via update_design") and points to list_personalizable_products for satisfying productRef. Clear usage context, though it doesn't say when to prefer create over update on an existing draft.

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