Skip to main content
Glama
zabaglione

MCP Server for Unity

by zabaglione
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

project_status

Check Unity MCP server connection status to verify connectivity with Unity projects for script creation, asset management, and building operations.

Instructions

Check Unity MCP server connection status (simple connectivity test only)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/tools/unity-mcp-tools.ts:441-451 (handler)
    The executeTool method's switch case handler for 'project_status' tool. It calls adapter.isConnected() to check Unity server status and returns a simple text response.
    case 'project_status': {
  const connected = await this.adapter.isConnected();
  const status = connected ? 'Unity server is connected and ready' : 'Unity server is not connected or not responding';
  
  return {
    content: [{
      type: 'text',
      text: status
    }]
  };
}
  • src/tools/unity-mcp-tools.ts:204-210 (registration)
    Tool registration in getTools() method, defining name, description, and empty inputSchema for project_status.
      name: 'project_status',
  description: 'Check Unity MCP server connection status (simple connectivity test only)',
  inputSchema: {
    type: 'object',
    properties: {}
  }
},
  • src/tools/unity-mcp-tools.ts:206-210 (schema)
    Input schema definition for project_status tool (no required parameters).
      inputSchema: {
    type: 'object',
    properties: {}
  }
},

Tool Definition Quality

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the tool's behavioral scope ('simple connectivity test only'), which is helpful context. However, it doesn't mention what the test entails, potential failure modes, or what 'connection status' means in practice.

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?

The description is a single, efficient sentence that front-loads the core purpose ('Check Unity MCP server connection status') and adds qualifying detail ('simple connectivity test only') without any wasted words.

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-parameter tool with no annotations and no output schema, the description is adequate but has gaps. It explains the purpose and scope, but doesn't describe what the output might look like (e.g., success/failure indicators) or error conditions, which would be helpful given the lack of structured output information.

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?

With 0 parameters and 100% schema description coverage, the baseline is 4. The description adds value by clarifying that this is a 'simple connectivity test only,' which provides semantic context beyond the empty schema.

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 explicitly states the verb ('Check') and resource ('Unity MCP server connection status'), making the purpose specific and clear. It distinguishes from siblings by specifying this is a 'simple connectivity test only' rather than project operations like folder_create or script_read.

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?

The description provides clear context for when to use this tool ('simple connectivity test only'), implying it's for verifying server availability before other operations. However, it doesn't explicitly state when NOT to use it or name specific alternatives among the siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zabaglione/mcp-server-unity'

If you have feedback or need assistance with the MCP directory API, please join our Discord server