Skip to main content
Glama
Sign In
Unreal Engine MCP

Unreal Engine MCP

by FFZackFair92
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

preset_download_polyhaven

Download Poly Haven CC0 assets (textures, models, HDRIs) into the local library, specifying resolution and format. Optionally override the destination folder.

Instructions

Scarica un asset Poly Haven (CC0) nella libreria locale.

Args: asset_id: id dell'asset, es. "brick_wall_02". resolution: "1k" | "2k" | "4k" | "8k". formats: ["jpg"] per texture, ["gltf"] per modelli, ["hdr"] per HDRI. destination: cartella alternativa alla libreria.

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": {
      "asset_id": "<asset_id>"
    },
    "name": "preset_download_polyhaven"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatsNo
asset_idYes
resolutionNo2k
destinationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It discloses that the asset is downloaded to a local library and specifies parameter options, but it does not mention side effects (e.g., overwriting, errors on invalid IDs), rate limits, or any output details.

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?

The description is concise and front-loaded with the main purpose. The Args section could be formatted as bullet points for quicker scanning, but every sentence is necessary and there is no redundancy.

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?

Given 4 parameters, no output schema, and no annotations, the description covers all parameters with allowed values. It lacks information on return values (e.g., success/failure) and error handling, but provides sufficient detail for correct invocation.

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

Parameters5/5

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

Schema description coverage is 0%, so the description compensates fully. It explains each parameter: asset_id with an example, resolution with enumerated values (1k, 2k, 4k, 8k), formats with type-specific examples (jpg for texture, gltf for models, hdr for HDRI), and destination as an alternative folder. This adds critical meaning beyond the bare 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 states the specific action: 'Scarica un asset Poly Haven (CC0) nella libreria locale' (Download a Poly Haven asset into the local library). It includes a verb (download) and a resource (Poly Haven asset), clearly distinguishing it from siblings like preset_download_ambientcg or preset_download_kenney.

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 usage for Poly Haven assets but does not explicitly state when to use this tool versus other download tools (e.g., for different sources) or search tools. No exclusions or alternative suggestions are provided.

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