Skip to main content
Glama

layout_live_edit

Live-edit the styling of an existing game layout (e.g. layout='citadel_hud_top_bar').

Instructions

Live-edit the styling of an existing game layout (e.g. layout='citadel_hud_top_bar').

css: an edited copy of one of the layout's stylesheets. stylesheet: which one, in any form ('hud/foo', 'styles/hud/foo.css', 's2r://panorama/styles/hud/foo.vcss'); default: the layout's include with the layout's own name, else its only include (an error lists the choices). Get the original with ui_source. Declarations you added or changed are applied live as a persistent inline-style sheet named 'live:<path under styles/ without extension>', e.g. 'live:hud/foo' (@define values are substituted; pseudo-classes/animations and removed declarations can't be applied live — use compile_source for those). Undo with css_clear('live:hud/foo').

unsafe_reload=True instead compiles an edited copy of the layout (xml and/or css) and re-loads it into the live panels. This CRASHES the game for layouts whose root is a C++ panel type (most HUD/dashboard layouts, e.g. CitadelHudTopBar); the bridge skips panels it knows are unsafe and lists them under 'skipped'. Only use it for plain Panel-rooted layouts.

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_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
uiNoauto
cssNo
xmlNo
layoutYes
stylesheetNo
unsafe_reloadNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so: it names the persistent inline-style sheet and its naming convention, notes that @define values are substituted, enumerates what cannot be applied live, and documents the undo path. The unsafe_reload section discloses a hard crash risk, which panel types are affected, and that unsafe panels are skipped and reported under 'skipped'.

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?

Purpose is front-loaded and nearly every sentence carries operational information, so the density is earned. The stylesheet-resolution sentence is a long parenthetical run that is harder to parse than necessary, but no content is obviously padding.

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 six-parameter mutation tool with zero schema descriptions and no annotations, the description is unusually complete: it covers persistence, undo, live-editing limits, and crash risk. The unexplained 'ui' parameter and the fact that xml is only described indirectly through unsafe_reload keep it from being fully complete.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate; it does well for css (an edited copy of a stylesheet), stylesheet (three accepted path forms plus default-resolution logic and an error that lists choices), layout (example value), and unsafe_reload/xml via the reload paragraph. The 'ui' parameter (default 'auto') is never explained anywhere, which is a real gap at 0% coverage.

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?

Opens with a specific verb and resource ('Live-edit the styling of an existing game layout') and immediately anchors it with a concrete example (layout='citadel_hud_top_bar'). It also sketches the two operating modes (live inline-style sheet vs unsafe_reload) so the agent knows precisely what class of operation this is.

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 routes to siblings: ui_source to fetch the original, compile_source for pseudo-classes/animations and removed declarations, css_clear('live:hud/foo') to undo. It also draws a hard when-not line for unsafe_reload ('Only use it for plain Panel-rooted layouts') backed by a crash warning, which is exactly the alternative-selection guidance an agent needs.

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