Skip to main content
Glama

Find mockups

search_mockups
Read-onlyIdempotent

Search Drint's library of ready 3D packaging and print mockups (about a thousand models: paper boxes, rigid gift boxes, paper bags, shipping cartons, bottles, jars, cans, cups, labels, flexible pouches, mugs, apparel, signage, posters, books, calendars). Use a few plain words for the product, e.g. "kraft paper bag", "tuck end box", "hộp quà Tết", "chai mỹ phẩm". A Drint product code ("D-10234", or "D-10234-3" for one size) finds that product. Returns models with id, code, name, size in mm and a picture; shows them as a grid the user can click to open in 3D.

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": {
      "query": "<query>"
    },
    "name": "search_mockups"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoThe user's language (vi, en, th, zh…). Default en.
limitNoHow many models (default 8).
queryYesWhat to look for, a few words, English or Vietnamese.

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.1/5.0
Behavior3/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 profile is covered. The description does add genuine behavioral context beyond them: the result fields (id, code, name, size in mm, picture) and that results render as a clickable grid that opens in 3D. It says nothing about empty results, how many are returned by default in practice, or ranking behavior, so it is useful but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and scope are front-loaded in the first clause, and the product-code rule that an agent most needs is stated plainly. The long parenthetical category list ("mugs, apparel, signage, posters, books, calendars") adds colour but is the one part that could be trimmed without losing calling 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?

With only three parameters, no nested objects and no output schema, the description carries the return-value burden and does so (id, code, name, size in mm, picture, grid rendering). Remaining gaps are minor: no mention of result-count behaviour or what happens when nothing matches.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns above that by explaining the query parameter's two input modes with concrete syntax ("D-10234" vs "D-10234-3" for one size) and by showing multilingual example queries. lang and limit are left entirely to their schema descriptions, which is acceptable given full coverage.

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?

A specific verb ("Search") plus a precisely scoped resource ("Drint's library of ready 3D packaging and print mockups"), further narrowed by an enumerated catalogue of model types and a stated size (~1000). It is clearly distinguishable from siblings such as open_mockup (which opens one) and get_dieline/list_dielines (dielines, not mockups).

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?

Gives concrete query-construction guidance — "use a few plain words" with four worked examples in English and Vietnamese — and states the alternative input mode (a Drint product code, optionally with a size suffix). It does not explicitly say when to prefer this over open_mockup or when a dieline tool is the better fit, so the routing signal is implicit rather than spelled out.

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.