Skip to main content
Glama

Open a 3D mockup

open_mockup
Read-onlyIdempotent

Show one Drint mockup in an interactive 3D viewer the user can rotate, zoom, recolour and resize. Take the id from search_mockups. Optional: colour (a colour or material name, or its number from 0), and a custom size in millimetres (length, width, height).

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": {
      "id": "<id>"
    },
    "name": "open_mockup"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe model id from search_mockups, e.g. "gift-ceramic-30".
langNoThe user's language (vi, en, th, zh…). Default en.
colourNoA colour / material name the model offers, or its number (0 = first).
width_mmNo
height_mmNo
length_mmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / lang / enum
      Previous value: -[
      -  "zh-Hant",
      -  "fil",
      -  "tet",
      -  "vi",
      -  "en",
      -  "zh",
      -  "ja",
      -  "ko",
      -  "mn",
      -  "th",
      -  "km",
      -  "lo",
      -  "my",
      -  "id",
      -  "ms",
      -  "hi",
      -  "ur",
      -  "bn",
      -  "ne",
      -  "si",
      -  "ta",
      -  "dz",
      -  "dv",
      -  "kk",
      -  "uz",
      -  "ky",
      -  "tg",
      -  "tk",
      -  "fa",
      -  "ps",
      -  "ar",
      -  "he",
      -  "tr",
      -  "az",
      -  "hy",
      -  "ka",
      -  "el",
      -  "es",
      -  "pt",
      -  "fr"
      -]New value: +[
      +  "zh-Hant",
      +  "fil",
      +  "tet",
      +  "vi",
      +  "en",
      +  "zh",
      +  "ja",
      +  "ko",
      +  "mn",
      +  "th",
      +  "km",
      +  "lo",
      +  "my",
      +  "id",
      +  "ms",
      +  "hi",
      +  "ur",
      +  "bn",
      +  "ne",
      +  "si",
      +  "ta",
      +  "dz",
      +  "dv",
      +  "kk",
      +  "uz",
      +  "ky",
      +  "tg",
      +  "tk",
      +  "fa",
      +  "ps",
      +  "ar",
      +  "he",
      +  "tr",
      +  "az",
      +  "hy",
      +  "ka",
      +  "el",
      +  "es",
      +  "pt",
      +  "fr",
      +  "de"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / lang / enum
      Previous value: -[
      -  "vi",
      -  "en",
      -  "th",
      -  "zh",
      -  "id",
      -  "es",
      -  "pt",
      -  "ms",
      -  "fil",
      -  "fr",
      -  "ja",
      -  "ko",
      -  "hi"
      -]New value: +[
      +  "zh-Hant",
      +  "fil",
      +  "tet",
      +  "vi",
      +  "en",
      +  "zh",
      +  "ja",
      +  "ko",
      +  "mn",
      +  "th",
      +  "km",
      +  "lo",
      +  "my",
      +  "id",
      +  "ms",
      +  "hi",
      +  "ur",
      +  "bn",
      +  "ne",
      +  "si",
      +  "ta",
      +  "dz",
      +  "dv",
      +  "kk",
      +  "uz",
      +  "ky",
      +  "tg",
      +  "tk",
      +  "fa",
      +  "ps",
      +  "ar",
      +  "he",
      +  "tr",
      +  "az",
      +  "hy",
      +  "ka",
      +  "el",
      +  "es",
      +  "pt",
      +  "fr"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / lang / enum
      Previous value: -[
      -  "vi",
      -  "en",
      -  "th",
      -  "zh",
      -  "id",
      -  "es",
      -  "pt",
      -  "ms",
      -  "fil",
      -  "fr",
      -  "ja",
      -  "ko"
      -]New value: +[
      +  "vi",
      +  "en",
      +  "th",
      +  "zh",
      +  "id",
      +  "es",
      +  "pt",
      +  "ms",
      +  "fil",
      +  "fr",
      +  "ja",
      +  "ko",
      +  "hi"
      +]
  4. First observed

TDQS

A4.2/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, so the safety burden is covered. The description adds behavior the annotations cannot: this opens an interactive viewer the end user manipulates, and recolour/resize happen inside that viewer rather than as a persisted mutation. It stops short of saying what, if anything, is returned to the agent.

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: capability and scope first, then the id source and optional inputs. No filler and nothing buried.

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 six-parameter, output-schema-less tool, the description covers the required id, the colour format, and the size units that the schema leaves blank. Remaining gaps (language handling, what the agent receives back after opening the viewer, behaviour on an unknown colour) are minor but real.

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 50% – the three size parameters carry only min/max with no descriptions, and the description compensates by stating they are a custom size in millimetres in length/width/height order. It also clarifies the colour parameter accepts a name or a zero-based number. The lang parameter gets no mention, though the schema documents it, so the net value above the schema is modest.

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 ("Show one Drint mockup") plus the concrete affordances of the target surface (rotate, zoom, recolour, resize), which tells an agent exactly what kind of action this is. The scoping word "one" plus the pointer to search_mockups separates it from list/search siblings.

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 the agent to search_mockups as the source of the required id, which is real when-to-use guidance. It does not say when to prefer a sibling such as send_to_3d_studio or open_my_project over this viewer, so an exclusion is missing.

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.