Skip to main content
Glama

project_info

Retrieve Unity project details including render pipeline, version, platform, and path to facilitate project analysis and setup.

Instructions

Get comprehensive Unity project information including render pipeline details, project path, Unity version, and platform info

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Main handler logic for the 'project_info' tool. Calls adapter.getProjectInfo(), performs auto-deploy if needed, and formats the response as structured text output.
            case 'project_info': {
              const result = await this.adapter.getProjectInfo();
              
              // Auto-deploy scripts if needed
              await this.autoDeployScripts();
              
              return {
                content: [{
                  type: 'text',
                  text: `Unity Project Information:
    Project Path: ${result.projectPath}
    Project Name: ${result.projectName || 'N/A'}
    Unity Version: ${result.unityVersion}
    Platform: ${result.platform}
    Is Playing: ${result.isPlaying}
    Render Pipeline: ${result.renderPipeline || 'Unknown'}
    Render Pipeline Version: ${result.renderPipelineVersion || 'N/A'}`
                }]
              };
            }
  • Tool registration and schema definition in getTools() method. Defines name, description, and empty input schema (no parameters required).
    {
      name: 'project_info',
      description: 'Get comprehensive Unity project information including render pipeline details, project path, Unity version, and platform info',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    },
  • Core implementation helper in UnityHttpAdapter. Proxies the tool call to Unity HTTP server endpoint 'project/info' via the generic call() method.
    async getProjectInfo(): Promise<any> {
      return this.call('project/info');
    }
  • Supporting helper method that uses getProjectInfo() to auto-deploy MCP scripts on project access.
    private async autoDeployScripts(): Promise<void> {
      try {
        const result = await this.adapter.getProjectInfo();
        await this.deployService.deployScripts({ 
          projectPath: result.projectPath,
          forceUpdate: false 
        });
      } catch (error: any) {
        console.error(`[Unity MCP] Failed to auto-deploy scripts: ${error.message}`);
      }
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While it indicates this is a read operation ('Get'), it doesn't specify whether it requires specific permissions, has rate limits, returns structured data, or handles errors. The description is insufficient for a tool that presumably accesses project metadata.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/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 and lists specific information types retrieved. Every word contributes to understanding what the tool does without unnecessary elaboration.

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?

For a tool that retrieves comprehensive project information with no annotations and no output schema, the description is inadequate. It doesn't explain what format the information returns in, whether it's structured data or raw text, what happens if the project isn't accessible, or how to interpret the retrieved details.

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 has zero parameters with 100% schema description coverage, so the schema already fully documents the parameter situation. The description appropriately doesn't waste space discussing parameters that don't exist, earning a baseline score of 4 for this dimension.

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?

The description clearly states the tool's purpose with specific verbs ('Get comprehensive Unity project information') and resources ('Unity project'), making it immediately understandable. However, it doesn't explicitly distinguish this from its sibling 'project_status' tool, which appears to serve a related but potentially different function.

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?

The description provides no guidance on when to use this tool versus alternatives like 'project_status' or other sibling tools. It mentions what information is retrieved but offers no context about appropriate use cases, prerequisites, or limitations.

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