Skip to main content
Glama

add_pcg_component

Idempotent

Attach a procedural generation component to an actor and optionally assign a PCG graph, turning a plain actor or volume into a rule-based scatterer of meshes and points.

Instructions

Attach a PCG component (the procedural generation engine) to an actor and optionally point it at a PCG graph -- what turns a plain actor or volume into something that scatters meshes and points by rule. Idempotent: an actor that already has one gets it back. The component generates within the actor's BOUNDS, so on a volume with no brush geometry it produces zero instances with no error at all -- confirm the extent with get_actor_bounds first. Then run generate_pcg_component and inspect with get_pcg_component_info.

Returns: { actor_name, component_name, already_existed, graph_path, graph_assigned }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actor_nameYesDisplay label or internal name of the target editor-world actor (required)
pcg_graph_pathNoOptional /Game/... path of a UPCGGraph to assign to the component

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 declare idempotentHint=true, destructiveHint=false, readOnlyHint=false, and the description reinforces idempotency while adding behavioral context beyond annotations: the bounds constraint that silently yields zero instances with no error. That gotcha is genuinely useful and not derivable from structured fields.

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-loaded with the core action, then behavior, then the gotcha, then the workflow, then the return shape. Dense but every sentence carries actionable information with no filler.

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?

For a mutation tool with no output schema, the description compensates by stating the return shape and covering idempotency, the silent-failure bounds caveat, and the follow-up workflow. Nothing an agent needs to call it correctly is missing.

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 coverage is 100%, so the schema already fully documents actor_name and pcg_graph_path. The description confirms pcg_graph_path is optional and explains its semantic effect at a high level, but adds little syntax or format detail beyond the schema. Baseline 3 applies 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?

Names a specific verb and resource ('Attach a PCG component') and adds a parenthetical explaining what the PCG engine is and what the component turns an actor into. An agent can distinguish this from siblings like generate_pcg_component or cleanup_pcg_component from the description alone.

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?

Provides explicit workflow guidance: confirm extent with get_actor_bounds first, then run generate_pcg_component, then inspect with get_pcg_component_info. It also explains the idempotency behavior (existing component is returned). This is explicit when/next-step guidance with named alternatives.

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