Skip to main content
Glama
Sign In
JANCTION Render

JANCTION Render

by JasmyLab-JANCTION
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

asset_search

Read-onlyIdempotent

Find free CC0 3D models, PBR textures, and HDRIs on Poly Haven by keyword to furnish a Blender scene without uploading files. Returns asset IDs, sizes, and entry files ready for rendering.

Instructions

Find free CC0 3D models, PBR textures or HDRIs on Poly Haven by words ('wooden chair', 'forest hdri') to furnish a scene without uploading files; no GPU time. For product shots of something the user has no model for: asset_search(''), then render_preview(scene_script='import jr_assets; jr_assets.import_model("")', assets=['polyhaven:'], preset='product') gives 4 studio shots on a plain backdrop (import_model removes Blender's untouched startup cube first). Each result has a spec 'polyhaven:' to pass in assets, its size in metres and the entry file. In the scene script: import jr_assets, then jr_assets.import_model('', location=(x, y, z), scale=1.0) returns the objects, jr_assets.material('') builds a material and jr_assets.apply(obj, mat) assigns it, jr_assets.world_hdri('', strength=1.0) lights the world. 'polyhaven:@2k' fetches 2k textures (1k by default).

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": {
      "query": "<query>"
    },
    "name": "asset_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo'models' (default) | 'textures' | 'hdris'.models
queryYesWords to search Poly Haven for (name, tags, category), e.g. 'wooden chair' or 'forest hdri'.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.4.119
    • addedInput schema / properties / kind / description
      Added value: +"'models' (default) | 'textures' | 'hdris'."
    • addedInput schema / properties / query / description
      Added value: +"Words to search Poly Haven for (name, tags, category), e.g. 'wooden chair' or 'forest hdri'."
  2. Addedv0.2.2

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), and the description adds real context on top: no uploads, no GPU time, each result carries a 'polyhaven:<id>' spec, size in metres and entry file, and 'polyhaven:<id>@2k' selects 2k textures with 1k as default.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is well front-loaded with purpose and scope, but the tail is a dense run-on that documents import_model/material/apply/world_hdri library APIs — useful downstream but arguably not this tool's job, making the description longer and harder to scan than needed for a 2-parameter search.

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

Completeness5/5

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

For a tool embedded in a multi-step render pipeline, the description closes the loop: what results look like, how the spec id feeds render_preview's assets, and how assets get imported into a scene. An output schema exists, yet the description's extra notes on result contents remain appropriately targeted.

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 100%, so the two parameters are already documented; the description nonetheless adds the @2k texture-resolution suffix convention and the spec format used downstream in the assets array, which is meaning the schema does not carry.

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+source: find free CC0 3D models, PBR textures or HDRIs on Poly Haven by words. Instantly separable from siblings like render_preview or scene_info, and the example queries ('wooden chair', 'forest hdri') pin down the expected input style.

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

Usage Guidelines5/5

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

Gives explicit when-to-use contexts (furnish a scene without uploading files; product shots for items the user has no model for) and spells out the alternative workflow with the sibling it hands off to: asset_search then render_preview with assets=['polyhaven:<id>']. This is exactly the routing guidance an agent needs.

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