blender-mcp

Overview Schema Source Related Servers Discussions Admin

get_sketchfab_model_preview

Retrieve a Sketchfab model's thumbnail by its UID to visually confirm the model before downloading it.

Instructions

Get a preview thumbnail of a Sketchfab model by its UID.
Use this to visually confirm a model before downloading.

Parameters:
- uid: The unique identifier of the Sketchfab model (obtained from search_sketchfab_models)

Returns the model's thumbnail as an Image for visual confirmation.

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": {
      "uid": "<uid>"
    },
    "name": "get_sketchfab_model_preview"
  }
}

Input Schema

Name	Required	Description	Default
`uid`	Yes
`user_prompt`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.6.0Aug 10, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description must convey behavior. It mentions retrieving a thumbnail and its purpose but does not state whether the operation is read-only or any side effects. It is fairly transparent for a simple read operation.

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?

The description is concise with two clear sentences, avoiding unnecessary details while covering the essential purpose and usage.

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?

It adequately describes the return value as an Image for visual confirmation. For a simple tool, it provides enough context, though it lacks potential error scenarios or prerequisites. Given the simplicity, it is reasonably complete.

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?

The description explains the 'uid' parameter as the identifier obtained from search_sketchfab_models, adding meaningful context beyond the schema. However, the 'user_prompt' parameter is left unexplained, leaving a gap in 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?

Clearly states it retrieves a preview thumbnail for a Sketchfab model, specifying the action and resource. It distinguishes from sibling tools like search_sketchfab_models and download_sketchfab_model by focusing on preview retrieval.

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 instructs to use it to visually confirm a model before downloading, providing a clear use case. It does not mention when not to use it, but the guidance is sufficient for the intended purpose.

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