Skip to main content
Glama
Sign In
Unity MCP Server

Unity MCP Server

by rachitkumarrastogi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_unused_assets_estimate

Estimates Unity assets not referenced by build scenes to identify cleanup candidates; verify each with find_references before any manual deletion.

Instructions

Unused-asset estimate: assets not referenced by build scenes (confirm via find_references; never auto-delete).

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_unused_assets_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
top_nNoUnused samples to return, default 30

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.2

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does reasonably well: it discloses that results are an estimate rather than ground truth, scopes them to build scenes only (a meaningful limitation), and requires verification before action. It still does not explain what 'estimate' omits (e.g., dynamically loaded or addressables assets) or the return shape.

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?

A single compact sentence that front-loads the core definition and packs the caveat and safety note into parentheticals without waste.

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?

For a single-parameter read-only estimate with no output schema, the description covers what it returns conceptually, its reliability caveat, and the required verification step. Missing only a note on what the estimate excludes or how results are ordered/capped.

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?

Only one optional parameter (top_n) and the schema already documents it at full coverage, including the default of 30. The description adds no additional meaning about the parameter, 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 (assets not referenced by build scenes) and frames the output as an estimate, which distinguishes it from inventory siblings like get_scene_referenced_assets or list_large_assets. It does not explicitly contrast with the inverse tool, but the scope is clear enough to select it.

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?

Gives an explicit follow-up action: confirm results via find_references, and an explicit prohibition: never auto-delete. It does not state when to prefer this estimate over a full reference scan, but the verify-then-act workflow is clearly conveyed.

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