Skip to main content
Glama
oc4n

MCP for Blender

by oc4n
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

search_assets

Search Poly Haven, Sketchfab, and Poly Pizza for 3D models, HDRIs, and textures by plain-language query, then pass asset IDs to import into Blender.

Instructions

Search a library of existing assets. The sources:
- polyhaven: HDRIs, PBR textures and realistic models, all CC0. Search understands intent and
  synonyms ("couch" finds sofas).
- sketchfab: a large catalogue of user-made models, realistic and specific ones included;
  licences and face counts vary per model.
- polypizza: stylised low-poly models, CC0 or CC-BY (credit the creator).

Parameters:
- source: polyhaven, sketchfab or polypizza.
- query: What you're looking for, in plain words.
- asset_type: polyhaven only: hdris, textures, models or all.
- category: Optional. polyhaven: a category path ("Metal/Sheet & Corrugated"). sketchfab:
  comma-separated categories. polypizza: e.g. "Furniture & Decor", "Nature", "Animals".
- attributes: polyhaven only: filters like {"weather": "clear"}; an unknown key errors with the
  valid ones.
- min_size_m: polyhaven only: minimum real-world size in metres. Use 2+ for walls, floors and
  ground so textures don't visibly repeat.
- licence: polypizza only: "CC0" or "CC-BY".
- animated: polypizza only: animated models only.
- limit: Number of results.
- previews: Attach thumbnails of the first N results (max 6; polyhaven and sketchfab). Cheaper
  than importing the wrong asset.
- user_prompt: The user's own words describing what they want, quoted verbatim.

Results include each asset's id; pass it to import_asset.

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
sourceYes
licenceNo
animatedNo
categoryNo
previewsNo
asset_typeNoall
attributesNo
min_size_mNo
user_promptNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.4

TDQS

A4.5/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden and mostly delivers: it warns unknown attribute keys error with the valid list, caps previews at 6 and notes the cost tradeoff, and requires crediting CC-BY creators on polypizza. It omits auth requirements, rate limiting, and failure modes for unknown sources.

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?

Front-loads the multi-source framing as a bulleted list, then a parallel parameter list in schema order. Every line carries substantive information despite the length, which is justified by 11 parameters and three divergent backends.

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?

With no output schema, the description covers the critical return detail ('Results include each asset's id; pass it to import_asset') and previews semantics. It does not describe the rest of the result shape (licence, face count, dimensions) that an agent would need to judge fitness without importing.

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

Parameters5/5

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

Schema coverage is 0% and the description compensates fully, documenting all 11 parameters including which source each applies to (asset_type, attributes, min_size_m, licence, animated, previews are all scoped). It even supplies example values for category and attributes, adding meaning the schema cannot.

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?

States a specific verb+resource ('Search a library of existing assets') and immediately enumerates the three distinct backends with their content types, so an agent knows what corpus it is querying. The closing line routing ids to import_asset separates it cleanly from the import_asset and generate_3d siblings.

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

Usage Guidelines4/5

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

Per-source guidance effectively tells the agent when to use each: polyhaven for CC0 PBR/HDRI, sketchfab for realistic/specific user models with varying licences, polypizza for stylised low-poly. It also gives a concrete heuristic ('Use 2+ for walls, floors and ground'). It lacks explicit when-not-to-use this tool versus generate_3d, which keeps it below 5.

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