Skip to main content
Glama

unity_component_set_reference

Set an object reference on a component property by specifying a scene GameObject, asset path, or instance ID. Resolves references more accurately than general property setters for wiring GameObjects, components, and assets.

Instructions

Set an object reference on a component property. Dedicated tool for wiring references between GameObjects, components, and assets. More powerful than set_property for ObjectReference fields — supports resolution by asset path, scene GameObject name, component type, or instance ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoHierarchy path or name of the target GameObject
instanceIdNoInstance ID of the target GameObject (alternative to path)
componentTypeNoComponent type containing the property (optional — will auto-search all components)
propertyNameYesName of the ObjectReference property to set
assetPathNoAsset path to assign (e.g. 'Assets/Materials/MyMat.mat', 'Assets/Prefabs/Enemy.prefab')
referenceGameObjectNoName or hierarchy path of a scene GameObject to assign
referenceComponentTypeNoWhen referencing a scene object, get a specific component instead of the GameObject itself (e.g. 'Camera', 'AudioSource')
referenceInstanceIdNoInstance ID of the object to assign
clearNoSet to true to clear/null the reference
portNoTarget Unity instance port for parallel-safe routing. Get this from unity_select_instance. When working with multiple Unity instances, ALWAYS include this parameter.
Behavior3/5

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

The description explains the tool's behavior (sets references, supports various resolution methods) and mentions the clear parameter. However, no annotations are provided, so the description carries the burden. It could disclose side effects or error cases.

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 with three sentences, front-loading the purpose and key differentiator. However, the list of resolution methods could be streamlined.

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 no output schema, the description adequately covers the tool's inputs and behavior. It is complete for a parameter-setting tool with many sibling tools, but lacks info on return values or error handling.

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 parameters are well-described in the schema. The description adds some context (e.g., 'more powerful than set_property') but does not add significant meaning beyond schema descriptions for most parameters.

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 sets object references on component properties, distinguishes it from set_property for ObjectReference fields, and lists supported resolution methods (asset path, scene GameObject name, component type, instance ID).

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

Usage Guidelines4/5

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

The description explains when to use this tool over set_property (for ObjectReference fields) and mentions resolution methods, but does not explicitly state when not to use it or provide alternatives for other cases.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AnkleBreaker-Studio/unity-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server