Skip to main content
Glama

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 handler function get_sketchfab_status in src/blender_mcp/server.py, which communicates with Blender via send_command to retrieve the status of Sketchfab integration.
    @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:
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 disclosure burden. It partially satisfies this by stating the return value ('a message indicating whether Sketchfab features are available'), but omits details about what 'enabled' entails (API keys, network, addon state), error conditions, or side effects. For a zero-annotation tool, more behavioral context could be provided.

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?

Two efficient sentences with zero waste. The first sentence establishes purpose, the second discloses return behavior. Every sentence earns its place and the description is appropriately front-loaded.

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 low complexity (no parameters, simple boolean check), no annotations, and no output schema, the description is reasonably complete. It explains what is checked and what is returned. It could be improved by mentioning the specific implication (e.g., whether download_sketchfab_model will succeed), but covers the essentials adequately.

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 zero parameters (empty object), which establishes a baseline score of 4 per the calibration rules. The description appropriately does not invent parameters, though it could explicitly confirm no configuration is required.

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 uses a specific verb ('Check') and resource ('Sketchfab integration') and explicitly limits scope to 'in Blender'. It distinguishes clearly from siblings like get_hunyuan3d_status, get_hyper3d_status, and get_polyhaven_status by specifying 'Sketchfab', and from action-oriented siblings like download_sketchfab_model by stating this is a status check.

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

Usage Guidelines3/5

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

The description states what the tool does but does not explicitly state when to use it versus alternatives (e.g., 'Use this before downloading Sketchfab models'). The usage is implied by the 'status' nature of the tool, but lacks explicit guidance on prerequisites or relationship to sibling tools like download_sketchfab_model.

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