Skip to main content
Glama
Sign In
polyhaven-mcp

polyhaven-mcp

by RN0000
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

search_assets

Filter and retrieve assets by type (hdris, textures, models) and categories from PolyHaven's public library.

Instructions

Returns a list of assets, optionally filtered by type and categories.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoFilter to assets of a particular type. Can be hdris/textures/models/all.
categoriesNoA comma-separated list of categories to filter by. Only assets that match all categories specified will be included.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It only states it returns a list with optional filters, omitting details like pagination, ordering, concurrency, or whether it is a read-only operation.

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?

The description is a single concise sentence, front-loaded with the main purpose. No unnecessary words, every part is essential.

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?

Given the absence of annotations and output schema, and the tool being a search function, the description lacks details on result format, error handling, or limitations. It feels incomplete for a search tool.

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

Parameters3/5

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

Schema description coverage is 100%, with both parameters described in the schema. The description adds 'optionally filtered', but this is already implied by the schema's optional nature. No additional semantic value beyond the schema.

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?

The description clearly states 'Returns a list of assets', specifying the action and resource, and mentions optional filtering. It distinguishes from sibling tools like get_asset_info and get_categories, which are more specific lookups.

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?

The description does not provide guidance on when to use this tool vs. alternatives like get_asset_files or get_asset_info. No context about usage context or prerequisites is given.

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