Skip to main content
Glama

unity_advanced_tool

Execute specialized Unity tools for animation, prefabs, physics, shaders, terrain, particles, UI, profiling, and more. Discover available tools via unity_list_advanced_tools.

Instructions

Execute an advanced/specialized Unity tool by name. Use unity_list_advanced_tools to discover available tools and their parameters. This provides access to 200+ specialized tools for animation, prefabs, physics, shaders, terrain, particles, UI, profiling, and more.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toolYesThe tool name to execute (e.g. "unity_animation_create_controller", "unity_shadergraph_create")
paramsNoParameters to pass to the tool. Use unity_list_advanced_tools to see required parameters.
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?

With no annotations provided, the description carries the full burden. It states this is a 'specialized' tool execution, but does not disclose any behavioral traits such as error handling, performance implications, or whether it is safe to call repeatedly. A score of 3 reflects that it gives basic context but lacks depth.

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 three sentences, front-loading the purpose and linking to a sibling tool. It is concise and avoids redundancy, though the second sentence could be integrated.

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

Completeness3/5

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

Given the tool's complexity (200+ specialized tools, no output schema), the description is somewhat complete but lacks details on return values or error handling. It relies heavily on the list tool for parameter details.

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 baseline is 3. The description adds context for the 'port' parameter (parallel-safe routing) and 'tool' parameter (examples), but does not add meaning beyond the schema for 'params' (just says to use list tool).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it executes an advanced/specialized Unity tool by name, which is a specific verb+resource. It mentions accessing 200+ specialized tools, distinguishing it from the sibling unity_list_advanced_tools which discovers tools.

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?

It explicitly says to use unity_list_advanced_tools to discover available tools and parameters, providing clear context on how to use this tool. However, it does not mention when not to use it or alternatives beyond that.

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