Skip to main content
Glama
Sign In
Unity MCP Server

Unity MCP Server

by rachitkumarrastogi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_texture_import_heaviness

Audit texture import settings to find heavy textures by flagging 2048+ caps, Read/Write enabled, missing mipmaps, and Crunch usage, returning the top N offenders.

Instructions

Texture import audit: 2048+ caps, Read/Write enabled, missing mipmaps, Crunch usage.

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

Input Schema

NameRequiredDescriptionDefault
top_nNoHeaviest textures to return, default 20

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.2

TDQS

C2.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the concrete checks performed (over-2048 max size, Read/Write enabled, missing mipmaps, Crunch compression), which is real behavioral content beyond the schema. However, it omits that this is a read-only scan, whether it spans the whole project, expected cost, and the shape of the returned report.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single line contains no filler and the criteria are front-loaded, but it reads as an incomplete fragment rather than a structured description. Brevity here edges into under-specification rather than efficient communication.

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?

For an audit/inspection tool with no output schema and no annotations, the description does not explain what the returned results contain (per-texture entries, sizes, flags) or how the findings are ordered. The audit criteria are the only substance an agent gets to decide relevance and interpret output.

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 coverage is 100% and the single parameter top_n is documented in the schema as 'Heaviest textures to return, default 20'. The description adds no additional semantics about ranking or truncation behavior, so the baseline 3 applies.

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

Purpose3/5

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

The description is a noun-phrase fragment listing audit criteria (2048+ caps, Read/Write enabled, missing mipmaps, Crunch) rather than a verb+resource statement of what the tool returns. An agent can infer it audits texture import settings, but the framing ('audit:') never says it produces a ranked list of the heaviest textures. It gives no differentiation from the sibling get_texture_meta.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as get_texture_meta for per-texture metadata or get_build_size_estimate for size impact. The agent must infer the use case entirely from the tool name and the list of criteria.

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