Skip to main content
Glama

unity_set_object_reference

Assign an object reference to a component property using a hierarchy path, instance ID, or asset path. Useful for linking scene objects or assets.

Instructions

[LEGACY] Set an object reference on a component. Prefer unity_component_set_reference (richer resolution).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoHierarchy path of the target GameObject
portNoUnity instance port (from unity_select_instance). Always include it when multiple instances run.
instanceIdNoInstance ID (alternative to path)
propertyNameYesName of the ObjectReference property to set
componentTypeNoComponent type name (optional - will search all components)
referencePathNoAsset path of the reference (for assets like prefabs, materials, textures)
referenceGameObjectNoName/path of a GameObject in the scene (for scene references)
Behavior2/5

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

No annotations are provided, and the description only mentions it is legacy. It does not disclose side effects, error behaviors, or resolution differences beyond calling the alternative 'richer'.

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?

The description is extremely concise (one sentence) with no wasted words. It includes a legacy marker and a recommendation for an alternative.

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

Completeness2/5

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

Given 7 parameters and no output schema or annotations, the description is too sparse. It lacks guidance on parameter interactions, required combinations, or typical workflows.

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?

The schema has 100% coverage with descriptions for all 7 parameters, so the baseline is 3. The tool description adds no parameter-level information, but the schema sufficiently explains 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 what the tool does ('Set an object reference on a component') and distinguishes it from the preferred sibling 'unity_component_set_reference' by labeling it legacy.

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 explicitly recommends preferring the alternative tool, but does not clarify when this legacy tool should be used (e.g., fallback or compatibility scenarios).

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