Skip to main content
Glama

tests-run

Run Unity tests with filtering by test mode, assembly, namespace, class, or method. Get detailed results including pass/fail status, messages, stack traces, and console logs. Use EditMode for faster iteration.

Instructions

Execute Unity tests and return detailed results. Supports filtering by test mode, assembly, namespace, class, and method. Recommended to use 'EditMode' for faster iteration during development.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
testModeNoTest mode to run. Options: 'EditMode', 'PlayMode'. Default: 'EditMode' Values: [EditMode, PlayMode]1
testAssemblyNoSpecific test assembly name to run (optional). Example: 'Assembly-CSharp-Editor-testable'
testNamespaceNoSpecific test namespace to run (optional). Example: 'MyTestNamespace'
testClassNoSpecific test class name to run (optional). Example: 'MyTestClass'
testMethodNoSpecific fully qualified test method to run (optional). Example: 'MyTestNamespace.FixtureName.TestName'
includePassingTestsNoInclude details for all tests, both passing and failing (default: false). If you just need details for failing tests, set to false.false
includeMessagesNoInclude test result messages in the test results (default: true). If you just need pass/fail status, set to false.true
includeStacktraceNoInclude stack traces in the test results (default: false).false
includeLogsNoInclude console logs in the test results (default: false).false
logTypeNoLog type filter for console logs. Options: 'Log', 'Warning', 'Assert', 'Error', 'Exception'. (default: 'Warning') Values: [Error, Warning, Log]2
includeLogsStacktraceNoInclude stack traces for console logs in the test results (default: false). This is huge amount of data, use only if really needed.false
requestIdNo
Behavior2/5

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

No annotations provided, so description must carry full behavioral burden. It only states 'execute tests' without disclosing side effects, permissions, or whether results are synchronous. Lacks detail on return value behavior.

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 wasted words. Front-loaded with purpose, then filtering capability, then usage recommendation.

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?

Despite 12 parameters and no output schema, description omits return value details, synchronization behavior, and potential state changes. Incomplete for agent to fully understand tool.

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 92% with detailed parameter descriptions. Description adds only a generic mention of filtering, adding minimal value beyond 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?

Description clearly states it executes tests and returns results, with specific filtering capabilities. Distinguishes from siblings since no other test tool exists.

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?

Recommends EditMode for faster iteration, implying PlayMode for full simulation. Provides clear context for when to use each mode, but no explicit exclusions or alternatives.

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/butterlatte-zhang/unity-ai-bridge'

If you have feedback or need assistance with the MCP directory API, please join our Discord server