Skip to main content
Glama
Sign In
headless-unity-mcp

headless-unity-mcp

by Shonas301
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

unity_compile

Compile all Unity assemblies and detect compile errors by parsing the Unity log for 'error CS' entries.

Instructions

Import and compile all assemblies. The verdict is a error CS grep of the unity log, never the exit code — unity exits 0 on compile errors.

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": "unity_compile"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceNo
queue_wait_timeout_sNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and reveals a critical non-obvious behavior: success is determined by grepping the unity log for 'error CS', not the exit code, since Unity exits 0 on compile errors.

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?

Two concise sentences, each adding essential information: the first states the function, the second clarifies a crucial behavior. No unnecessary fluff.

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?

While the core purpose and a key behavior are covered, the description lacks parameter semantics and usage alternatives. Given no annotations and an output schema, it is only partially complete for a tool of this complexity.

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

Parameters2/5

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

Schema description coverage is 0%, and the description does not explain the 'workspace' or 'queue_wait_timeout_s' parameters. The parameter names hint at their meaning but the description adds no semantics.

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?

The description clearly states the action ('Import and compile all assemblies') with a specific verb and resource, distinguishing it from sibling tools like unity_build and unity_test.

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 description implies usage for compilation but provides no explicit when-to-use guidance or alternatives. The verdict clarification is more behavioral than usage-focused.

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