Skip to main content
Glama

get_sketchfab_model_preview

Retrieve a thumbnail preview of a Sketchfab model using its UID to verify the model visually 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

  • The handler for the get_sketchfab_model_preview tool, which communicates with Blender via send_command to retrieve a thumbnail.
    @telemetry_tool("download_sketchfab_model")
    @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"])
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses the return type ('Image for visual confirmation'), but lacks operational details like rate limits, validity of UIDs, image format/size, or network dependency on Sketchfab's API.

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?

Four compact sentences with zero redundancy: purpose statement, usage guidance, parameter documentation, and return value. Front-loaded with the core action. Structured logically despite not using strict markdown sections.

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?

Adequate for a single-parameter retrieval tool without output schema. Description explains the return value (Image) and establishes sibling relationships. Minor gap: no error handling guidance (e.g., invalid UID behavior).

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 0% (uid property lacks description), but description fully compensates by explaining the parameter is 'obtained from search_sketchfab_models,' providing crucial semantic context for tool chaining. Minor deduction for not specifying UID format constraints.

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?

Description provides specific verb ('Get a preview thumbnail'), resource ('Sketchfab model'), and scope ('by its UID'). Clearly distinguishes from sibling 'download_sketchfab_model' (preview vs. download) and 'search_sketchfab_models' (specific retrieval vs. search).

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?

Explicitly states 'Use this to visually confirm a model before downloading,' establishing clear workflow context. Also references sibling 'search_sketchfab_models' as the UID source, creating explicit tool chaining guidance.

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/omniconnexsynapse/blender-mcp'

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