Skip to main content
Glama

WELANDA Engraving Designer

Get handoff link

get_handoff_link
Read-onlyIdempotent

Get the signed handoff deeplink plus a short English summary to present to the customer ("Engraving … on … Personalization +…€"). The customer fine-tunes and checks out themselves.

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>"
    },
    "name": "get_handoff_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoEditor locale for the deeplink (de, en, sv, nb, da, fr, es, it). Default de.
designIdYesThe dsg_… id to hand off to the customer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world. Beyond that, the description discloses the return payload (a signed deeplink plus a formatted summary string, with an example) and the handoff workflow, which is real added context. It does not mention link expiry, reuse limits, or any signing/auth caveats that would matter for a signed token.

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 sentences, front-loaded with the returned resource, followed by the customer-facing workflow context. No filler and nothing redundant with the schema.

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 simple two-parameter read tool with full annotation coverage and no output schema, the description adequately explains what is returned and who consumes it. The only meaningful omission is the lifetime/validity of the signed link, which an agent handing off to a customer would benefit from knowing.

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?

Both parameters are fully documented in the schema (100% coverage), so the schema carries parameter meaning. The description adds no syntax or constraint detail for designId or locale, though it implicitly clarifies that the summary stays English regardless of the deeplink locale — a useful nuance but not parameter documentation.

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 specific verb and resource — 'Get the signed handoff deeplink' — and adds what else comes back (a short English summary). It also conveys the outcome ('customer fine-tunes and checks out themselves'), making it clearly distinct from get_design or render_preview without naming them explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the phrase 'to present to the customer' and 'The customer fine-tunes and checks out themselves' signals the handoff scenario. There is no explicit when-to-use/when-not guidance and no named alternative (e.g., get_design) for cases where the caller wants design data instead of a customer-facing link.

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