Skip to main content
Glama

debugger

Inspect and troubleshoot Unity applications by evaluating expressions, examining object state, and managing breakpoints.

Instructions

Unity debugging utilities for inspection and troubleshooting. Actions:

  • evaluate_expression: Evaluate a C# expression in the current context

  • get_stack_trace: Get current stack trace (when paused or from last exception)

  • list_breakpoints: List all breakpoints (requires external debugger)

  • dump_object: Get detailed dump of an object's fields and properties

  • invoke_method: Invoke a method on a GameObject or component

  • get_static_field: Get value of a static field from a type

  • set_static_field: Set value of a static field

  • call_static_method: Call a static method on a type

  • debug_log: Log structured debug information

  • get_component_values: Get all serialized values from a component

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesDebugger action to perform
maxDepthNoMaximum depth for object dump (default: 3)
objectIdNoInstance ID of the object
typeNameNoFull type name including namespace (e.g., "UnityEngine.Application")
debugDataNoStructured data for debug_log
fieldNameNoStatic field name
expressionNoC# expression to evaluate
fieldValueNoValue to set for static field
methodArgsNoArguments for method invocation
methodNameNoMethod name to invoke
objectPathNoHierarchy path of the object
componentTypeNoComponent type name (e.g., "Transform", "MyScript")
includePrivateNoInclude private fields in dump
Behavior3/5

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

Annotations (readOnlyHint=false) indicate possible mutations. The description includes notes like 'when paused or from last exception' for get_stack_trace and 'requires external debugger' for list_breakpoints, adding some context beyond annotations. However, it doesn't detail side effects or auth requirements for other actions.

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

Conciseness4/5

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

The description is concise and front-loaded with the purpose. It uses a list format which is efficient for a composite tool. However, the list is somewhat lengthy but structured well.

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?

Given the tool's complexity (13 parameters, 10 sub-actions, no output schema), the description is incomplete. It lacks details on output formats, how parameters combine with actions, and typical usage patterns.

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 description coverage is 100%, so the schema already documents all parameters. The description adds no additional parameter-specific meaning beyond listing actions. Baseline 3 is appropriate.

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?

The description states 'Unity debugging utilities for inspection and troubleshooting' and lists specific actions, clearly indicating the tool's purpose as a composite debugging meta-tool. However, it doesn't differentiate from sibling tools like get_console_logs or watch_console.

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 no guidance on when to use this tool vs. alternatives. It lists actions but does not explain context or exclusions. For example, it doesn't advise when to use debugger over get_console_logs for logging.

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/joel-wehr/unity-mcp'

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