Skip to main content
Glama

get_sketchfab_status

Check if Sketchfab integration is enabled in Blender to verify availability of 3D asset import and export 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' tool. It uses the @mcp.tool() decorator for registration and implements the logic by sending a 'get_sketchfab_status' command to the Blender connection, processing the result to return a status message indicating if Sketchfab integration is enabled.
    @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)}"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.0
    • addedInput schema / title
      Added value: +"get_sketchfab_statusArguments"
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It notes it returns a message but doesn't specify if it's a boolean, string, or the exact content. No side effects are mentioned, but it's implied to be non-destructive.

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?

Two concise sentences with front-loaded purpose. Efficient, though could be slightly more explicit about the return format.

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?

For a zero-parameter tool with no output schema, the description adequately covers the purpose and behavior. It could mention the return type (e.g., boolean or string) for completeness.

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?

No parameters exist, and schema coverage is 100%. The description adds value by explaining the purpose but doesn't need to compensate for missing param info.

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 checks if Sketchfab integration is enabled in Blender, using a specific verb and resource. It is distinct from sibling tools like download_sketchfab_model, but doesn't explicitly differentiate.

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?

No guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. The description only states what it does, not when it's appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.