Skip to main content
Glama
Sign In
Unity MCP Server

Unity MCP Server

by rachitkumarrastogi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_localization_stack

Retrieves the Unity Localization package and Locale/StringTable assets to show AI assistants the project's broader localization stack without opening the Unity Editor.

Instructions

Localization package + Locale/StringTable assets (broader than get_localization_tables).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.2

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It discloses what the result spans (package plus Locale/StringTable assets), which is useful scope information, but says nothing about read-only semantics, permissions, size, or whether the scan is expensive — notable for a zero-param tool that presumably walks the project.

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 sentence that front-loads the resource and puts the differentiating clause in parentheses. Every clause earns its place with no filler.

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?

With no output schema, the description must convey what an agent receives, and 'package + assets' is only a sketch — the shape of a 'stack' and whether it includes settings or configuration is unstated. Adequate to identify the tool, not enough to predict its result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so there is nothing for the description to disambiguate; baseline is 4. The schema is trivially complete and the description correctly adds no parameter chatter.

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 the resource (localization package plus Locale/StringTable assets) and distinguishes scope from a named sibling, which lets an agent tell it apart from get_localization_tables without opening either schema. It stops short of a precise verb — 'get' is implied by naming only — but the resource is concrete.

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 parenthetical 'broader than get_localization_tables' implicitly routes the agent here when the narrower tables tool is insufficient, which is real but weak guidance. It never states when NOT to use it, nor the condition that makes the broader scope necessary.

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