Skip to main content
Glama
Sign In
Unity MCP Server

Unity MCP Server

by rachitkumarrastogi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_addressables_duplicates

Detect duplicate Addressables asset GUIDs across groups, with optional custom profile path reporting.

Instructions

Addressables duplicate check: asset GUIDs in multiple groups + optional profile path notes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_addressables_duplicates"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_profilesNoAlso report custom build/load profile paths

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.2

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden. 'Duplicate check' implies a non-mutating inspection and it discloses what is reported (duplicate GUIDs plus optional profile path notes), but says nothing about permissions, cost on large projects, or whether results are grouped per asset.

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?

One compact, front-loaded sentence that names the primary output first and the optional extra second. The '+' shorthand is slightly telegraphic but costs no clarity.

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?

A simple optional-flag read tool, so little is required, but with no annotations and no output schema the description is the only place to learn the return shape. It hints at GUIDs-in-multiple-groups plus profile notes yet does not describe how duplicates are grouped or what else accompanies each entry.

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% and the single parameter already documents 'Also report custom build/load profile paths'. The description's phrase 'optional profile path notes' echoes rather than extends that, so the baseline 3 applies.

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?

States a specific resource and check: asset GUIDs that appear in multiple Addressables groups, which is a distinct concern from the inventory-oriented sibling get_addressables_info. The verb is nominally 'check' rather than an explicit 'list/find', but the semantics are unambiguous.

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 implied use case (detect duplicate/double-included assets across groups) follows from the description, but there is no explicit when-to-use, when-not-to-use, or reference to a sibling alternative such as get_addressables_info. An agent must infer call conditions from the purpose alone.

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