Fab MCP

by ThreeNativeHQ

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Get a Poly Haven asset

polyhaven_get_asset

Read-onlyIdempotent

Get normalized metadata, authorship, dimensions, and CC0 license information for one Poly Haven asset.

Instructions

Get normalized metadata, authorship, dimensions, and CC0 license information for one Poly Haven asset.

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": {
      "assetId": "<assetId>"
    },
    "name": "polyhaven_get_asset"
  }
}

Input Schema

Name	Required	Description	Default
`assetId`	Yes

Output Schema

Name	Required	Description	Default
`id`	Yes
`url`	Yes
`lods`	No
`name`	Yes
`tags`	Yes
`type`	Yes
`authors`	Yes
`donated`	No
`license`	Yes
`category`	No
`provider`	Yes
`filesHash`	No
`polycount`	No
`attributes`	Yes
`categoryId`	No
`dimensions`	No
`description`	No
`publishedAt`	No
`thumbnailUrl`	No
`downloadCount`	No
`maxResolution`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.1Sep 14, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare read-only, open-world, idempotent, and non-destructive behavior. The description adds context about the type of metadata returned (authorship, dimensions, license). No contradictions.

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?

Single sentence, 13 words, front-loaded with verb and resource. Every word is informative; no redundancy or fluff.

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?

Output schema exists, so return values are defined. The description covers the main output components. However, it could mention that the asset ID comes from a search tool. Still, it is sufficient for a simple retrieval tool.

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

Parameters1/5

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

Schema description coverage is 0%, so the description must explain the parameter. It does not mention 'assetId' or how to obtain it. The parameter is required, yet the description lacks any guidance on its value.

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 verb 'Get', the resource 'one Poly Haven asset', and specifies the returned information: normalized metadata, authorship, dimensions, and CC0 license. It distinguishes this tool from search and list siblings.

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

Usage Guidelines3/5

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

The description implies use when you need metadata for a specific Poly Haven asset, but it does not explicitly mention when not to use it or provide alternatives. Given many sibling tools, more guidance would be helpful.

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

Deploy Server