Skip to main content
Glama
Sign In
Unity MCP Server

Unity MCP Server

by rachitkumarrastogi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_build_report_summary

Summarizes a Unity build report by listing size, scenes, errors, and warnings, defaulting to the newest report to support quick build health review.

Instructions

Summarize a build report: size, scenes, errors/warnings. Defaults to newest report.

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

Input Schema

NameRequiredDescriptionDefault
top_nNoMax entries per list, default 20
report_pathNoReport path from list_build_reports; omit for newest

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.2

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden; it does disclose the useful default selection behavior (newest report) and the categories of content summarized. It does not state what happens if no reports exist, whether the operation is strictly read-only, or anything about result formatting or size 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 short sentences, zero waste, with the core purpose and the default behavior front-loaded. Nothing in the text is redundant filler.

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?

For a simple two-parameter read tool with full schema coverage and no output schema, the description adequately conveys what the summary contains (size, scenes, errors/warnings) and how the target report is chosen. Only edge-case behavior (no reports available) is left unstated.

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 100%, so both parameters are already documented, including top_n's default of 20. The description only reinforces the report_path default ('newest report') and never mentions top_n, so it adds little beyond the schema baseline.

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?

States a specific verb (summarize) and resource (build report) plus the contents returned: size, scenes, errors/warnings. It implicitly contrasts with list_build_reports, which the schema references for obtaining a report_path, but the description itself does not explicitly differentiate from siblings like get_build_size_estimate or get_scene_summary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Defaults to newest report' implies the common case (omit report_path to get the latest), and the schema points to list_build_reports as the source for an explicit path. There is no explicit when-not guidance or named alternative for cases where a full report rather than a summary is wanted.

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