Skip to main content
Glama
Sign In
Unity MCP Server

Unity MCP Server

by rachitkumarrastogi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_build_target_info

Retrieves the active Unity build target and platform from ProjectSettings, so you can identify the current build configuration without opening the Unity Editor.

Instructions

Get active build target / platform from ProjectSettings.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

No annotations are supplied, so the description carries the burden; 'Get ... from ProjectSettings' does imply a read-only, side-effect-free lookup of current editor state. It says nothing about the return format or whether the value reflects the editor's selected target versus a saved build profile setting.

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 short sentence with the action and data source front-loaded and no filler. Nothing could be trimmed without losing meaning.

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 trivial zero-parameter read the description is close to sufficient, but with no output schema the agent cannot know whether the result is a plain string, an enum name, or a structured object, nor how to interpret it across platforms.

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 zero parameters and the schema is empty, so there is nothing further to document; baseline of 4 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 verb and resource: retrieve the active build target/platform, sourced from ProjectSettings. An agent can tell this returns the current platform rather than a report or profile list, though it does not explicitly contrast itself with siblings like get_project_info or get_platform_build_hints.

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?

No when-to-use guidance, no exclusions, and no mention of adjacent tools such as get_platform_build_hints or get_project_info that an agent might otherwise choose. Usage is only implied by the word 'active'.

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