Skip to main content
Glama
Sign In
polyhaven-mcp

polyhaven-mcp

by RN0000
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_asset_files

Retrieve download URLs for any PolyHaven asset by providing its unique ID slug, enabling direct file access.

Instructions

File list for a specific asset, providing URLs to download the actual files.

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": {
      "id": "<id>"
    },
    "name": "get_asset_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe unique ID/slug of the asset.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

Without annotations, the description carries full burden. It states URLs are provided but does not disclose behavior like URL expiration, pagination, or whether all files are returned at once. Minimal transparency beyond basic purpose.

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 (13 words) that front-loads the key action and output. No wasted words.

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

Completeness3/5

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

Given the tool has one parameter and no output schema, the description is adequate for a simple list retrieval. However, it lacks details on output format (e.g., array of objects with URL properties), which could assist an agent in using the output. Slightly incomplete.

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%, so the schema already documents the 'id' parameter. The description adds no additional meaning beyond stating it is for a specific asset. Baseline 3 is appropriate as the description does not compensate beyond schema.

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?

The description clearly states the tool retrieves a file list for a specific asset and outputs download URLs. It uses a specific verb ('get') and resource ('asset files'), and the context of sibling tools (e.g., get_asset_info, search_assets) helps differentiate it.

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?

No explicit guidance on when to use this tool versus alternatives. The description does not mention prerequisites, when not to use it, or any context for selection. The implied usage is only through the tool name and description.

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