Skip to main content
Glama

history

Undo or redo recent Roblox Studio changes by specifying an action and step count, optionally targeting a Studio when multiple sessions are open.

Instructions

Undo or redo the last change(s) in Studio (every tool edit is recorded as an undo step).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "history"
  }
}

Input Schema

NameRequiredDescriptionDefault
stepsNoDefault 1.
actionYes
studioNoOptional. Target Studio (name substring, place id or id). Only needed when several Studios are open and none was selected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden. It does add a useful non-obvious behavior: every tool edit is recorded as an undo step. However, it does not explain redo-stack behavior, whether manual Studio edits are included, what happens when no history exists, or what the tool returns.

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?

The description is a single, front-loaded sentence with a compact parenthetical that adds context without waste. Every part earns its place.

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 three-parameter tool with no output schema, the description covers the core operation and one important recording behavior. Gaps remain around undo-stack edge cases, but the schema already documents the parameters, so the definition is mostly complete.

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 moderate at 67%, and the description does not add syntax or constraints for the action, steps, or studio parameters beyond what the schema already documents. The parenthetical about tool edits being undo steps loosely relates to the steps parameter but does not explain multi-step behavior.

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 action pair (undo/redo) and the resource it acts on (the last change(s) in Studio), which is enough to distinguish it from the inspection and editing siblings. It loses a point because 'last change(s)' and the tool name 'history' leave the exact scope slightly ambiguous, and the parenthetical only partially clarifies that scope as tool edits.

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?

Use is implied by the action verbs, and the schema makes the undo/redo choice explicit, but the description gives no guidance on when to choose this over other recovery or editing approaches, or when not to use it. There is no mention of alternatives or prerequisites such as having an existing undo step.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.