Skip to main content
Glama

get_sketchfab_status

Check if Sketchfab integration is enabled in Blender to verify 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 main handler function for the 'get_sketchfab_status' MCP tool. It uses the @mcp.tool() decorator for registration and @telemetry_tool for logging. The function sends a 'get_sketchfab_status' command to the Blender addon via the persistent connection and formats the response message.
    @telemetry_tool("get_sketchfab_status")
    @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)}"
  • The @mcp.tool() decorator registers the get_sketchfab_status function as an MCP tool.
    @mcp.tool()
  • Instruction in the asset_creation_strategy prompt recommending the use of get_sketchfab_status to check Sketchfab availability.
    Use get_sketchfab_status() to verify its status
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 the basic behavior: checking integration status and returning a message. However, it lacks details such as error handling (e.g., what happens if Blender isn't accessible), performance characteristics, or whether this is a read-only operation (implied but not stated). The description doesn't contradict annotations since none exist.

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 extremely concise and well-structured: two sentences that directly state the action and the return value. Every word earns its place, with no redundancy or fluff. It's front-loaded with the core purpose, making it easy to scan.

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 minimally adequate. It covers the basic purpose and return type but lacks context like error cases, integration specifics, or how the result informs other tools (e.g., 'download_sketchfab_model'). For a simple status check, it's passable 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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate. Baseline is 4 for zero parameters, as it avoids unnecessary repetition and focuses on the tool's purpose.

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.' It specifies the 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_hunyuan3d_status' or 'get_hyper3d_status', which have similar checking purposes for other 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 (e.g., whether Blender must be running), exclusions, or related tools like 'download_sketchfab_model' that might depend on this status check. Usage is implied by the purpose but not explicitly stated.

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

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