Skip to main content
Glama
Sign In
Unity MCP Server

Unity MCP Server

by rachitkumarrastogi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_building_blocks

Lists Unity 6.3 LTS Building Blocks—packages and sample assets with production-ready gameplay components—to inspect reusable project resources without the Editor.

Instructions

Unity 6.3 LTS Building Blocks: packages + sample assets with production-ready gameplay components.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.2

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and it discloses almost nothing: it does not say whether results are read-only, whether it scans the project or a registry, whether it enumerates all Building Blocks or a filtered subset, or what each entry contains. 'Production-ready gameplay components' is marketing phrasing rather than behavioral information.

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

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no padding, which is good, but it is not front-loaded with an action or a clear statement of what the agent gets back. Brevity here reflects under-specification rather than disciplined editing.

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 simple zero-parameter list tool the bar is low, but with no output schema and no annotations the description should at least say what the listing returns (names, package references, paths) and how it relates to the package-oriented siblings. Neither is present, so an agent has no basis for choosing this tool over list_packages.

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 takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. Schema coverage is 100% for the empty object.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a noun-phrase fragment ('Unity 6.3 LTS Building Blocks: packages + sample assets with production-ready gameplay components') with no verb, so the action (listing) is only implied by the tool name. It does carve out a distinct subject—Building Blocks composed of packages plus sample assets—but the overlap with sibling names list_packages and list_package_samples is not addressed, leaving the agent to guess the boundary.

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?

There is no when-to-use guidance at all: no statement of when to call this instead of list_packages, list_package_samples, or list_ai_prompt_or_config_assets. Usage is only inferable from the name, which is weak given that multiple siblings also enumerate packages and samples.

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