Sceneplane

Search the asset library

assets_search

Read-onlyIdempotent

Read-only search of existing 3D asset catalogs; returns real slugs for asset_library_import. For new models without an explicit/prior source choice, check relevant existing project assets and search available catalogs before building. Preview a few suitable results with source/license, then ask whether to reuse, adapt or build from scratch. Honor explicit from-scratch choices. source=polyhaven (default, CC0 — HDRIs, PBR texture sets, models) needs no setup. source=sketchfab searches public downloadable-model metadata (type=model only; import requires integrations_set provider=sketchfab; honor each hit's license).

Input Schema

Name	Required	Description	Default
`type`	Yes	Kind of library asset to search for.
`limit`	No	Maximum results to return (1–30).
`query`	No	Search terms or a Poly Haven category; empty lists popular assets.
`source`	No	Catalog to search. Sketchfab public search can work without a token; import needs an approved connection.	polyhaven

Output Schema

Name	Required	Description	Default
`items`	Yes
`rejections`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

changedInput schema / properties / source / description

Previous value: -"Asset catalog to search; Sketchfab requires a configured token."New value: +"Catalog to search. Sketchfab public search can work without a token; import needs an approved connection."

Changed2 schema fields changedOct 27, 2026

addedOutput schema / properties / items / items / properties / sourceAttribution
```
Added value: +{}
```

addedOutput schema / properties / rejections

Added value: +{
+  "items": {
+    "additionalProperties": {},
+    "properties": {
+      "reason": {
+        "type": "string"
+      },
+      "slug": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "slug",
+      "reason"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Changed8 schema fields changedOct 25, 2026
- removedOutput schema / properties / items / items / properties / license / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / items / items / properties / license / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / items / items / properties / maxResolution / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / items / items / properties / maxResolution / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / items / items / properties / polycount / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / items / items / properties / polycount / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / items / items / properties / thumbnailUrl / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / items / items / properties / thumbnailUrl / type
```
Added value: +[
+  "string",
+  "null"
+]
```
First observedSep 24, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond readOnlyHint/idempotentHint/openWorldHint: polyhaven needs no setup (CC0 HDRIs, textures, models), while sketchfab requires integrations_set provider=sketchfab for import, is limited to type=model, and each hit's license must be honored. Setup/auth and licensing constraints are exactly what annotations cannot convey.

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-loads purpose in the first clause and every sentence carries routing or constraint information. It is a dense paragraph that folds workflow coaching into one long run of clauses, which costs a little scannability but adds no filler.

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 an output schema present, return format needn't be explained, and the description still notes hits carry source/license. All decision-relevant context — default source, setup requirements, license obligations, downstream tool — is present; only minor detail like result paging is left implicit.

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 baseline is 3; the description still adds meaning the schema does not — that source=polyhaven is the default with no setup, and that sketchfab only works for type=model. It does not expand on query/limit semantics, so it sits just above baseline.

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?

Opens with a specific verb+resource+scope ('Read-only search of existing 3D asset catalogs') and names the downstream consumer ('returns real slugs for asset_library_import'), which distinguishes it from asset_library_import and asset_generate_3d. An agent can route correctly without opening any schema.

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?

Explicitly states when to search (no explicit/prior source choice; before building), what to do with results (preview a few with source/license, then ask reuse vs adapt vs build), and the exclusion ('Honor explicit from-scratch choices'). This is a genuine decision procedure, not implied guidance.

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

All Sceneplane tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?