Skip to main content
Glama
AnkleBreaker-Studio

Unity MCP Server

by AnkleBreaker-Studio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

unity_undo_history

Review which recorded MCP actions can still be reverted, including agent, target, and current Unity Undo state.

Instructions

Show which recorded MCP actions can still be reverted, with agent, target and current Unity Undo state.

Input Schema

NameRequiredDescriptionDefault
portNoUnity instance port (from unity_select_instance). Always include it when multiple instances run.
countNoMax actions to return, newest first (default 20).
agentIdNoOptional: only show actions from this agent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.35.6
    • addedInput schema / properties / agentId
      Added value: +{
+  "description": "Optional: only show actions from this agent.",
+  "type": "string"
+}
    • addedInput schema / properties / count
      Added value: +{
+  "description": "Max actions to return, newest first (default 20).",
+  "type": "number"
+}
    • changedInput schema / properties / port / description
      Previous value: -"Target Unity instance port for parallel-safe routing. Get this from unity_select_instance. When working with multiple Unity instances, ALWAYS include this parameter."New value: +"Unity instance port (from unity_select_instance). Always include it when multiple instances run."
  2. Addedv2.28.1

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully names the fields returned (agent, target, current Unity Undo state) and implies a read-only listing, but it does not state read-only behavior explicitly, nor mention permissions, ordering/pagination beyond the schema, or what it means for an action to no longer be revertible.

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?

A single front-loaded sentence with no filler or redundancy. Every clause (revertible actions, agent, target, Undo state) carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description must do more of the explanatory work. It partially covers returned content but omits ordering guarantees, response shape, and confirmation that the operation has no side effects, leaving gaps for a read tool of this kind.

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 all three parameters (port, count, agentId) are already documented, establishing the baseline of 3. The description's mention of 'agent' loosely corresponds to agentId but adds no syntax, format, or constraint details beyond the schema.

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 a specific verb ('show') and a well-scoped resource: recorded MCP actions that can still be reverted, plus agent, target, and Undo state. It is clearly distinct from the action-oriented siblings unity_undo, unity_undo_last, and unity_redo, though it never names them explicitly.

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 explicit when-to-use or when-not-to-use guidance. With siblings unity_undo and unity_undo_last present, a definition would ideally route the agent ('inspect history here, revert with unity_undo'), but the description leaves that inference entirely to the reader.

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