Skip to main content
Glama

WELANDA Engraving Designer

Replace design draft

update_design
Destructive

Replace a draft's design with a new full DesignDocumentV3 (version increments, previews invalidated). Same validation as create_design. Fails with CLAIMED once the customer has opened and claimed the draft in the editor.

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": {
      "designId": "<designId>",
      "design": "<design>"
    },
    "name": "update_design"
  }
}

Input Schema

NameRequiredDescriptionDefault
designYesA full replacement DesignDocumentV3 (no partial patches). Shape and limits come from list_personalizable_products.
designIdYesThe dsg_… id returned by create_design.

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 full replacement DesignDocumentV3 (no partial patches)."New value: +"A full replacement DesignDocumentV3 (no partial patches). 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.4/5.0
Behavior5/5

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

Beyond the destructiveHint/readOnlyHint annotations, the description discloses concrete behaviors the agent could not otherwise infer: the version number increments, previews are invalidated, validation mirrors create_design, and the call fails with CLAIMED after editor handoff. That is exactly the side-effect and failure-mode context a destructive tool needs.

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?

Two tight sentences, front-loaded with the operation and its replacement semantics, then the constraints and failure condition. Every clause carries information an agent needs; nothing is padding.

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?

For a destructive, nested-object mutation with no output schema, the definition covers side effects, validation parity, and the blocking error condition well. The one gap is that the DesignDocumentV3 shape itself is only delegated to list_personalizable_products rather than sketched, which is a reasonable but not fully self-contained choice.

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 both designId (dsg_… id from create_design) and the design object are already documented inline. The description only reinforces the no-partial-patch constraint and repeats that shape/limits come from list_personalizable_products, adding little beyond the schema — the baseline of 3 applies.

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 gives a specific verb and resource ("Replace a draft's design with a new full DesignDocumentV3") and immediately distinguishes itself from create_design by noting the shared validation and from partial-update tools with "no partial patches." An agent can tell this is a full-replacement mutation on an existing draft rather than a creation call.

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 establishes the operating context clearly: full replacement only, same validation as create_design, and a hard stop (CLAIMED) once the customer has opened the draft. It stops short of explicitly naming a sibling to use instead when the draft is claimed, so it falls just below an explicit when/when-not/alternatives statement.

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