Skip to main content
Glama

import_polyhaven_via_blender

Import Poly Haven assets into Blender by asset ID, with configurable asset type and resolution, using the addon-side download.

Instructions

Ask Blender to import a Poly Haven asset by id (addon-side download).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "asset_id": "<asset_id>"
    },
    "name": "import_polyhaven_via_blender"
  }
}

Input Schema

NameRequiredDescriptionDefault
asset_idYes
asset_typeNomodels
resolutionNo1k

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/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 does disclose that the asset is downloaded on the addon side, which is genuine behavioral context (network use, addon prerequisite), but it omits that the operation mutates the Blender scene, where the asset lands, and what happens on failure.

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?

A single front-loaded sentence with no filler. It is efficient, though its brevity contributes to the missing parameter and side-effect context rather than being trimmed of it.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter, unannotated mutation tool that triggers a download, one sentence is not enough. An output schema covers the return value, but prerequisites (Poly Haven addon installed), scene side effects, and the meaning of asset_type/resolution are all missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate and largely does not. Only 'by id' maps to asset_id; asset_type (default 'models') and resolution (default '1k') are never explained, and valid asset_type or resolution values are undocumented anywhere.

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?

States a specific verb and resource: import a Poly Haven asset by id, with the parenthetical clarifying that the download happens addon-side. Naming Poly Haven distinguishes it from the generic import_asset and import_external_asset siblings, though the description never explicitly contrasts them.

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?

Usage is only implied – the agent can infer this is for Poly Haven assets rather than local files, and 'addon-side download' hints at an addon/network dependency. There is no explicit when-to-use or when-not-to-use statement pointing at import_asset or import_external_asset.

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

Deploy Server

Other Tools