Skip to main content
Glama
Sign In
Unity MCP Server

Unity MCP Server

by rachitkumarrastogi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_prefab_dependencies

Lists asset paths referenced by a Unity prefab to support impact analysis and dependency tracking before making changes.

Instructions

List asset paths referenced by a prefab. Helps impact analysis.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "prefab_path": "<prefab_path>"
    },
    "name": "get_prefab_dependencies"
  }
}

Input Schema

NameRequiredDescriptionDefault
prefab_pathYese.g. Assets/Prefabs/Player.prefab

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.2

TDQS

A3.5/5.0
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 of behavioral disclosure. "List" clearly implies a read-only operation, and "asset paths referenced by a prefab" conveys the core behavior, but it does not clarify whether references are direct or transitive, what asset types are included, or what the response format looks like.

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 two short sentences with no wasted wording, and the core operation is front-loaded. "Helps impact analysis" adds a concise usage hint without bloating the definition.

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?

For a simple one-parameter read-only tool, the description covers the essential operation and a use case. However, with no output schema and no annotations, it could benefit from clarifying whether dependencies are direct or recursive and what the returned list contains, which would help an agent set expectations.

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 prefab_path parameter is already documented in the schema with an example. The description does not add meaning beyond that baseline; it merely says "by a prefab," which is already implied by the schema.

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 uses a specific verb ("List") and resource ("asset paths referenced by a prefab"), making the tool's function immediately clear. It implicitly distinguishes from siblings like get_prefab_script_guids and get_prefab_summary by focusing on asset paths, but it does not explicitly differentiate itself from those alternatives.

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

Usage Guidelines3/5

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

The phrase "Helps impact analysis" gives a contextual hint about when the tool is useful, but there is no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. Usage is therefore implied rather than stated.

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