Skip to main content
Glama

layout_live_revert

Restores the game's original layout to panels modified by unsafe live edits, undoing layout changes made during Panorama UI inspection.

Instructions

Re-load the game's original layout into panels changed by layout_live_edit(unsafe_reload=True). (For CSS edits made the safe way, use css_clear('live:').)

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": {
      "layout": "<layout>"
    },
    "name": "layout_live_revert"
  }
}

Input Schema

NameRequiredDescriptionDefault
uiNoauto
layoutYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 full burden. It implicitly discloses that live changes are overwritten by restoring the original layout, which is useful, but it does not say whether the revert is selective per panel, whether it is reversible, or what permissions/state are required. With an output schema present, return values need not be described, keeping this at an adequate level.

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 tight sentences, with the action stated first and the disambiguation in parentheses. Nothing is redundant and no sentence is padding.

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?

For a state-restoring operation with no annotations and 0% parameter documentation, the definition covers the what and the when but leaves argument meaning and scope-of-restore unstated. An output schema exists so return values need not be explained, but the input contract gap keeps it at minimum viable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain either parameter: it never says what the required 'layout' value should be (name, id, path) or what the 'ui' parameter (default 'auto') controls. The description mentions 'layout' only as a concept, not as an argument contract.

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 and resource ('Re-load the game's original layout') and scopes it to panels changed by layout_live_edit(unsafe_reload=True), which separates it from the CSS-clearing path. It is clear what the tool does, though the phrasing ties the purpose to a specific counterpart call rather than describing the resource generically.

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

Usage Guidelines5/5

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

Explicitly names when this applies (after an unsafe live edit) and names the alternative for the other case (css_clear with 'live:<stylesheet>'), including the exact argument form. An agent can route between this tool and css_clear without opening another schema.

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