Skip to main content
Glama
Sign In
Unity MCP Claude Code

Unity MCP Claude Code

by MauricePutinas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

install_editor_via_deeplink

Installs Unity editor via deep link to Hub GUI for cases requiring visual confirmation during installation.

Instructions

Startet die Editor-Installation über einen unityhub://-Deep-Link in der Hub-GUI (Alternative zur headless-Installation; nützlich wenn GUI-Bestätigung gewünscht).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "version": "<version>",
      "changeset": "<changeset>"
    },
    "name": "install_editor_via_deeplink"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionYes
changesetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations provide readOnlyHint=false, destructiveHint=false. Description adds that it uses deep link and opens Hub GUI, implying interactive behavior. Does not contradict annotations, provides useful context beyond them.

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?

Single sentence is concise and front-loaded, but fails to include parameter information, making it less efficient. Could be restructured to hint at params.

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?

No output schema, low schema coverage. Description explains purpose and usage context but omits parameter descriptions and any output/return behavior. Lacks completeness for a two-param tool.

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

Parameters1/5

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

Input schema has 0% description coverage, and description does not explain the two required parameters (version, changeset) at all. This is a major gap for a tool with only these params.

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

Purpose5/5

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

Clearly states it starts editor installation via a unityhub:// deep link. Distinguishes from headless installation (sibling tool 'install_editor') by describing it as an alternative for GUI confirmation.

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?

Explicitly says when to use: when GUI confirmation is desired, as alternative to headless. Does not specify when not to use, but context is clear.

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