Skip to main content
Glama

create_foliage_type

Creates and saves a FoliageType asset wrapping a static mesh, so it can be placed as foliage and tuned with property tools.

Instructions

Create and save a FoliageType asset (UFoliageType_InstancedStaticMesh) wrapping a static mesh, so it can be placed as foliage and tuned with set_foliage_type_properties. Creating the asset is safe; note that the tools that PLACE instances of it (add_foliage_instances, scatter_foliage_in_box, scatter_foliage_on_layer) can crash the editor, so plan to scatter via instanced-static-mesh components or PCG. For landscape GRASS driven by the terrain material use create_landscape_grass_type instead.

Returns: { name: string, package_path: string, asset_path: string, static_mesh: string, foliage_class: string, created: bool, already_exists: bool, mesh_set: bool, saved: bool, message: string }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesAsset name, e.g. FT_Grass
package_pathNoTarget content path, defaults to /Game/Foliage
static_mesh_pathYesFull path of the source StaticMesh

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already establish the safety profile (not read-only, not destructive), but the description adds substantial value: it clarifies that creating the asset is safe while the PLACEMENT tools (add_foliage_instances, scatter_foliage_in_box, scatter_foliage_on_layer) can crash the editor, and it recommends safer scatter paths (ISM components or PCG). This is exactly the kind of beyond-annotation context that prevents destructive mistakes.

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?

Front-loads the core action, then the caveat, then the alternative. Three sentences with no filler, and the Returns shape is compactly appended rather than padded.

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

Completeness5/5

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

Although no output schema exists, the description embeds a Returns object documenting name, package_path, asset_path, static_mesh, foliage_class, created, already_exists, mesh_set, saved, and message. Combined with the safety and routing guidance, an agent has everything needed to call and interpret this tool correctly.

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 name, package_path, and static_mesh_path. The description adds no syntax or format detail beyond what the schema provides. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb and resource ('Create and save a FoliageType asset (UFoliageType_InstancedStaticMesh) wrapping a static mesh') and names the sibling it is not (create_landscape_grass_type). An agent can distinguish it from adjacent foliage/landscape tools 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 routes the agent: use create_landscape_grass_type for landscape grass driven by terrain material, and gives when-not guidance by naming crash-prone placement tools to avoid. Includes both an alternative selection rule and a downstream workflow recommendation.

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