Skip to main content
Glama
ujs204

BlenderMCP

by ujs204

download_sketchfab_model

Download and import 3D models from Sketchfab directly into Blender using the model's unique identifier, enabling prompt-assisted 3D scene creation.

Instructions

Download and import a Sketchfab model by its UID.

Parameters:

  • uid: The unique identifier of the Sketchfab model

Returns a message indicating success or failure. The model must be downloadable and you must have proper access rights.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uidYes

Implementation Reference

  • MCP tool handler for downloading and importing Sketchfab models by UID. Forwards the request to the Blender addon via socket send_command and handles the response, logging errors and returning success/failure messages.
    @mcp.tool()
    def download_sketchfab_model(
        ctx: Context,
        uid: str
    ) -> str:
        """
        Download and import a Sketchfab model by its UID.
        
        Parameters:
        - uid: The unique identifier of the Sketchfab model
        
        Returns a message indicating success or failure.
        The model must be downloadable and you must have proper access rights.
        """
        try:
            
            blender = get_blender_connection()
            logger.info(f"Attempting to download Sketchfab model with UID: {uid}")
            
            result = blender.send_command("download_sketchfab_model", {
                "uid": uid
            })
            
            if result is None:
                logger.error("Received None result from Sketchfab download")
                return "Error: Received no response from Sketchfab download request"
                
            if "error" in result:
                logger.error(f"Error from Sketchfab download: {result['error']}")
                return f"Error: {result['error']}"
            
            if result.get("success"):
                imported_objects = result.get("imported_objects", [])
                object_names = ", ".join(imported_objects) if imported_objects else "none"
                return f"Successfully imported model. Created objects: {object_names}"
            else:
                return f"Failed to download model: {result.get('message', 'Unknown error')}"
        except Exception as e:
            logger.error(f"Error downloading Sketchfab model: {str(e)}")
            import traceback
            logger.error(traceback.format_exc())
            return f"Error downloading Sketchfab model: {str(e)}"
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions access rights and downloadability as constraints, which adds some context, but fails to describe critical behaviors such as what 'import' entails (e.g., file format, destination), potential side effects, error handling, or response format beyond a success/failure message. This leaves significant gaps for a tool that performs downloads and imports.

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?

The description is appropriately sized with three sentences: a purpose statement, parameter explanation, and return/constraint info. It's front-loaded with the main action, but the last sentence could be more integrated. There's minimal waste, though it could be slightly more structured for optimal clarity.

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?

Given the complexity of downloading and importing a model, no annotations, no output schema, and low schema coverage, the description is incomplete. It lacks details on the import process, output format, error conditions, and how it differs from sibling tools. This makes it inadequate for an agent to fully understand the tool's behavior and usage context.

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 adds meaning by explaining that 'uid' is 'The unique identifier of the Sketchfab model', which clarifies its purpose beyond the schema's basic 'string' type. However, with schema description coverage at 0% and only one parameter, this provides moderate value but doesn't fully compensate for the lack of schema details (e.g., format examples, validation rules).

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

Purpose4/5

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

The description clearly states the verb 'Download and import' and the resource 'Sketchfab model by its UID', making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'search_sketchfab_models' or 'import_generated_asset', which would be needed for a perfect score.

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?

The description provides minimal guidance with 'The model must be downloadable and you must have proper access rights', which hints at prerequisites but doesn't specify when to use this tool versus alternatives like 'search_sketchfab_models' for finding models or 'import_generated_asset' for other imports. No explicit when/when-not or alternative tool references are included.

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/ujs204/CLAUDE-BLENDER-MCP'

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