Skip to main content
Glama
Sign In
Unity MCP Server

Unity MCP Server

by rachitkumarrastogi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_platform_build_hints

Retrieve platform-specific build hints for Unity projects, covering PlayerSettings snippets, build targets, and related packages for Android, WebGL, and Unity 6.

Instructions

PlayerSettings snippets for Android/WebGL/etc., build target, and related packages (Unity 6 platform pass).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.2

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, no output schema, and zero parameters, the description carries the full behavioral burden and discloses little: it never says whether it reads the current project's settings, whether results are static reference snippets or project-derived, or what shape the response takes. The only behavioral signal is the implicit read-only nature of a 'get' tool.

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?

It is a single short fragment with no padding, which is good, but the terseness crosses into under-specification: 'etc.' and the unexplained 'hints' leave the reader guessing. Short is not the same as front-loaded and clear here.

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 zero-argument, no-output-schema lookup tool, the description does enumerate the content categories returned (settings snippets, build target, related packages), which is the minimum an agent needs to decide relevance. It still leaves the response format and the meaning of 'hints' unexplained, so it is only marginally adequate.

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 at the argument level. Baseline 4 applies for a zero-parameter definition.

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 names the resource being returned (PlayerSettings snippets, build target, related packages) and scopes it to a Unity 6 platform pass, so an agent can roughly tell what it fetches. But it is a noun phrase with no verb and no statement of what a 'hint' actually is, so the purpose stays vague rather than crisp.

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 pointer to a sibling such as get_build_target_info or get_render_pipeline_migration_hints, despite many adjacent build tools in the catalog. The parenthetical '(Unity 6 platform pass)' hints at a context but does not tell the agent when to choose this over those alternatives.

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