FGD Designers: fonts, mockups and design assets

Open the live 3D mockup editor

mockup_link

Read-only

A link to the free in-browser 3D mockup editor on a product and scene, with a preview image. The person drops in their design, turns it, changes light and scene, animates it, and exports a free 1600 px image, or a 4K image or MP4 video for $3.

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": {
      "product": "<product>"
    },
    "name": "mockup_link"
  }
}

Input Schema

Name	Required	Description	Default
`scene`	No	Optional. Not every product has every scene; the product's default scene is used when it has not.
`product`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

C2.3/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that a preview image accompanies the link, which is mildly useful, but spends most of its length on downstream editor features and pricing ($3 for 4K/MP4) that say nothing about this tool's behavior, link lifetime, or whether the link is persistent or per-session.

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

Conciseness2/5

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

A single run-on sentence that front-loads the useful clause but then trails into marketing copy about rotating, lighting, animating, and paid exports. Those clauses do not help an agent decide or invoke, so they fail the 'every sentence earns its place' test.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description must carry the return contract; it does say a link plus preview image is returned, which is the one genuinely load-bearing detail. But for a two-parameter tool with an undocumented required parameter and no guidance on link persistence or failure when a product lacks a scene, it is under-specified.

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

Parameters2/5

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

Schema coverage is 50%: scene is documented in the schema, product is not. The description mentions 'on a product and scene' but adds no meaning beyond the enum values, and does not explain the product parameter or the product/scene compatibility rule that the scene description hints at.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource ('a link to the free in-browser 3D mockup editor on a product and scene, with a preview image'), so an agent can infer it produces a shareable editor URL plus preview. However, the verb is implicit and the bulk of the sentence describes what the end user does inside the editor rather than what the tool itself does, and it draws no boundary against siblings like get_item or get_licence.

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

Usage Guidelines2/5

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

There is no statement of when to call this versus alternatives, no prerequisites, and no exclusions. The only conditional guidance in the whole definition lives in the scene parameter's schema description, not in the tool description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All FGD Designers: fonts, mockups and design assets tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?