Skip to main content
Glama
Sign In
Unity MCP Server

Unity MCP Server

by rachitkumarrastogi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

search_project

Search Unity projects by asset name pattern, script content pattern, or find assets that reference a given path.

Instructions

Combined search: by asset name pattern, script content pattern, and/or referrers of an asset path. Returns assets, scripts, and optionally referrers.

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

Input Schema

NameRequiredDescriptionDefault
name_patternNoe.g. Player or *Menu*
script_patternNoe.g. MonoBehaviour or GameManager
include_packagesNo
referrer_of_pathNoAsset path; returns assets that reference it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.2
  2. Removedv1.5.1
  3. Addedv1.5.0

TDQS

A4/5.0
Behavior3/5

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

No annotations provided, so description must disclose behavior. It mentions returns assets, scripts, optionally referrers but does not confirm read-only nature or discuss any limits.

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 sentences, front-loaded with 'Combined search', no filler. Each sentence provides distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequately describes the search functionality and returned types. Lacks mention of result size limits or pagination, but sufficient for a search tool with no output schema.

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

Parameters3/5

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

Schema coverage is 75% and already includes descriptions. Description adds little value beyond restating the parameters as part of combined search. No additional meaning for include_packages.

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 is a combined search by asset name pattern, script content pattern, and/or referrers. Distinguishes from sibling tools like search_assets_by_name and find_references by being a multi-criteria search.

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?

Implies use when searching by combination of name, script, or references. Does not explicitly contrast with siblings but the context of combined search 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