Skip to main content
Glama

WELANDA Engraving Designer

Get design draft

get_design
Read-onlyIdempotent

Fetch a draft's current document, status, version, claimed flag, handoff link and previews by its designId.

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_design"
  }
}

Input Schema

NameRequiredDescriptionDefault
designIdYesThe dsg_… id. Knowing the id grants access (128-bit + TTL).

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 readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so safety is covered. The description still earns credit by enumerating the returned payload (document, status, version, claimed flag, handoff link, previews), which is meaningful because no output schema exists. It omits error/expiry behavior despite the schema's TTL hint, keeping 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?

A single front-loaded sentence with the verb and resource first and the returned fields listed after. No preamble, no filler, and nothing that could be cut without losing information.

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 one-parameter read tool whose annotations cover the safety profile, the description is nearly complete, and the payload list compensates for the absent output schema. The remaining gap is behavioral edge cases: what happens with an expired or revoked id, which the schema's TTL note gestures at but the description never addresses.

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?

There is a single required parameter at 100% schema coverage, and the schema already documents the dsg_… format and its access-granting property. The description only restates that lookup is keyed by designId, adding no new syntax or format meaning, so the baseline 3 applies.

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?

States a specific verb (Fetch) and resource (a draft) and enumerates exactly what comes back: document, status, version, claimed flag, handoff link, previews. That enumeration implicitly separates it from narrower siblings like get_handoff_link, but the description never names an alternative explicitly, so it falls short of full sibling differentiation.

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 only implied: the agent must already hold a designId to call it, and the phrase 'by its designId' signals that precondition. There is no statement of when to prefer this over get_handoff_link or render_preview, and no exclusion of cases where a lighter sibling would do.

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