Skip to main content
Glama
mikeysrecipes

BlenderMCP

get_sketchfab_status

Check if Sketchfab integration is enabled in Blender to determine availability of 3D model sharing and collaboration features.

Instructions

Check if Sketchfab integration is enabled in Blender. Returns a message indicating whether Sketchfab features are available.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The @mcp.tool() decorated function that implements the get_sketchfab_status tool. It connects to Blender, sends the 'get_sketchfab_status' command, processes the result, and returns a status message.
    @mcp.tool()
    def get_sketchfab_status(ctx: Context) -> str:
        """
        Check if Sketchfab integration is enabled in Blender.
        Returns a message indicating whether Sketchfab features are available.
        """
        try:
            blender = get_blender_connection()
            result = blender.send_command("get_sketchfab_status")
            enabled = result.get("enabled", False)
            message = result.get("message", "")
            if enabled:
                message += "Sketchfab is good at Realistic models, and has a wider variety of models than PolyHaven."        
            return message
        except Exception as e:
            logger.error(f"Error checking Sketchfab status: {str(e)}")
            return f"Error checking Sketchfab status: {str(e)}"
Behavior2/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 of behavioral disclosure. It states the tool returns a message indicating availability, which is helpful, but doesn't cover other aspects like whether it's a read-only operation, potential errors (e.g., if Blender isn't running), or performance considerations. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 highly concise and well-structured, consisting of two clear sentences. The first sentence states the purpose, and the second explains the return value. There is no wasted text, and it's front-loaded with the core functionality, making it easy to parse quickly.

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

Completeness3/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 (0 parameters, no output schema, no annotations), the description is adequate but has gaps. It explains what the tool does and what it returns, but without annotations or output schema, it doesn't detail the format of the return message or potential edge cases. For a simple status check, this is minimally viable but could be more informative.

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?

The tool has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately doesn't mention any. This meets the baseline for tools with no parameters, as it avoids unnecessary details.

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 tool's purpose: 'Check if Sketchfab integration is enabled in Blender.' This is a specific verb ('Check') and resource ('Sketchfab integration in Blender'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'get_hyper3d_status' or 'get_polyhaven_status', which have similar checking purposes but for different integrations.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context (e.g., before downloading Sketchfab models), or exclusions. With sibling tools like 'download_sketchfab_model' and 'search_sketchfab_models', there's no indication of when this status check is necessary or optional, leaving usage unclear.

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

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