Skip to main content
Glama
Sign In
Unity MCP Server

Unity MCP Server

by rachitkumarrastogi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

find_scripts_by_content

Locate C# scripts matching a specified type or pattern, with optional namespace filtering to narrow results.

Instructions

Find C# scripts that contain a type or pattern (e.g. MonoBehaviour, ScriptableObject, or custom). Optionally filter by namespace.

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": {
      "pattern": "<pattern>"
    },
    "name": "find_scripts_by_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
patternYesPattern to search for, e.g. MonoBehaviour or a type name
namespace_filterNoOptional namespace pattern, e.g. Game.*

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only says 'find scripts' without specifying the return format (file paths? content snippets?), search scope (file names vs. content), case sensitivity, regex support, or performance implications. This is insufficient for an agent to reliably invoke and interpret results.

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 no fluff, front-loaded with purpose and examples. Every word earns its place.

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 exists, yet the description does not explain what the tool returns (e.g., list of file paths, matched content, count). For a search tool, this is a critical gap. Agent cannot know if response includes full file paths or just names.

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?

Schema coverage is 100% with descriptions, but the tool description adds concrete examples (e.g., 'MonoBehaviour', 'Game.*') that help the agent understand valid inputs beyond the schema. This adds meaningful value without repeating 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 clearly states the verb 'Find' and the resource 'C# scripts that contain a type or pattern', with concrete examples like MonoBehaviour. This distinguishes it from sibling tools like list_scripts (which lists all scripts) and find_references (which finds references to specific assets).

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 examples but lacks explicit guidance on when to use this tool versus alternatives like find_references or list_scripts. It does not state prerequisites, when not to use it, or how it differs from search_assets_by_name.

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