Skip to main content
Glama
opslon

BlenderMCP

by opslon

get_sketchfab_model_preview

Retrieve a Sketchfab model thumbnail using its UID to visually verify the model before downloading it into Blender.

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uidYes

Implementation Reference

  • Implementation of the 'get_sketchfab_model_preview' tool, which handles the request to the Blender connection and returns the model thumbnail.
    @mcp.tool()
    def get_sketchfab_model_preview(
        ctx: Context,
        uid: str
    ) -> Image:
        """
        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.
        """
        try:
            blender = get_blender_connection()
            logger.info(f"Getting Sketchfab model preview for UID: {uid}")
            
            result = blender.send_command("get_sketchfab_model_preview", {"uid": uid})
            
            if result is None:
                raise Exception("Received no response from Blender")
            
            if "error" in result:
                raise Exception(result["error"])
            
            # Decode base64 image data
            image_data = base64.b64decode(result["image_data"])
            img_format = result.get("format", "jpeg")
            
            # Log model info
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns a thumbnail 'as an Image for visual confirmation,' which is useful behavioral context. However, it lacks details on potential errors (e.g., invalid UID), rate limits, or authentication needs, leaving gaps for a tool with no annotation coverage.

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 front-loaded with the core purpose, followed by usage guidance and parameter details in a structured format. Every sentence adds value without redundancy, making it efficiently sized and well-organized.

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?

Given the tool's low complexity (1 parameter, no output schema, no annotations), the description is mostly complete: it covers purpose, usage, and parameter semantics. However, it lacks output details (e.g., image format or size) and error handling, which could be useful for an agent, though not critical for this simple tool.

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

Parameters5/5

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

The input schema has 0% description coverage, so the description must compensate. It adds significant meaning by explaining that 'uid' is 'The unique identifier of the Sketchfab model' and specifying it's 'obtained from search_sketchfab_models,' which clarifies the parameter's purpose and source beyond the bare schema.

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?

The description clearly states the tool's purpose with a specific verb ('Get') and resource ('preview thumbnail of a Sketchfab model'), and it distinguishes from siblings like 'download_sketchfab_model' by focusing on previewing rather than downloading. The phrase 'visually confirm a model before downloading' reinforces this distinction.

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

Usage Guidelines5/5

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

The description explicitly states when to use this tool ('Use this to visually confirm a model before downloading') and references a sibling tool ('search_sketchfab_models') as the source for the UID parameter, providing clear context and alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/opslon/blender-mcp-optimized'

If you have feedback or need assistance with the MCP directory API, please join our Discord server