Skip to main content
Glama
Apteryx-T

blender-mcp

by Apteryx-T
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

download_polyhaven_asset

Download and import Polyhaven HDRI, texture, or model assets into Blender by specifying asset ID, type, resolution, and optional file format.

Instructions

Download and import a Polyhaven asset into Blender.

Parameters:
- asset_id: The ID of the asset to download
- asset_type: The type of asset (hdris, textures, models)
- resolution: The resolution to download (e.g., 1k, 2k, 4k)
- file_format: Optional file format (e.g., hdr, exr for HDRIs; jpg, png for textures; gltf, fbx for models)
- user_prompt: The original user prompt that led to this tool call (for telemetry)

Returns a message indicating success or failure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asset_idYes
asset_typeYes
resolutionNo1k
file_formatNo
user_promptNo

Tool Definition Quality

B3.4/5.0
Behavior2/5

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

With no annotations, description carries full burden but only mentions success/failure. Missing details on blocking behavior, overwrite semantics, error cases, or side effects on Blender scene.

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?

Front-loaded purpose, then lists parameters. No fluff, but telemetry parameter description feels slightly out of place. Concise overall.

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?

Parameters are explained but behavioral aspects (import process, error handling) are absent. Output schema not provided, but description says 'returns message indicating success or failure', which is adequate.

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?

Schema coverage is 0%, so description compensates by listing parameters with examples (asset_type options, resolution common values, file_format per type). Adds meaning beyond schema titles.

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?

Description clearly states verb (download and import), resource (Polyhaven asset), and context (into Blender). Distinguishes from sibling download_sketchfab_model by specifying Polyhaven.

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 like search_polyhaven_assets or download_sketchfab_model. No explicit when/when-not criteria.

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/Apteryx-T/blender_mcp_test'

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