Skip to main content
Glama

make_responsive

Destructive

Converts Roblox UI Offset values to Scale across position, size, padding, and corner radius so interfaces adapt to different screen sizes; preview with dryRun first and skip runtime-driven elements.

Instructions

Make a UI subtree resolution-proof. Converts Offset→Scale across ALL the properties that break responsiveness — Position, Size, CanvasSize, CellSize, CellPadding, UIPadding, UICorner CornerRadius (validated formula: ÷ parent AbsoluteSize per axis; CornerRadius ÷ min-axis). Skips runtime-driven elements (tagged Draggable/Resizable, or in exclude) so it never shatters draggable/resizable panels. ALWAYS dryRun first to preview. modes: scale (default, Offset→Scale) · offset (reverse) · fit (root fills parent: Size {1,1} + Pos 0 + Anchor 0) · uiscale (keep Offset, add a UIScale + a real viewport-fit driver). Flags: aspectRatio (add UIAspectRatioConstraint at current aspect, skips layout-managed kids), minSize (UISizeConstraint 44×44 on buttons).

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": {
      "path": "<path>"
    },
    "name": "make_responsive"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoConversion mode (see the description). Default scale.
pathYesRoot of the UI to convert, e.g. "StarterGui.HUD.Panel". Dot path from the DataModel root, e.g. "Workspace.Map.Door" or "StarterGui.HUD.Frame". A leading "game." is optional; a duplicate sibling name takes the suffix Tufan prints, e.g. "Part (2)".
placeNoTarget place (PlaceId or project name). Defaults to the bound/sole connected place.
dryRunNopreview without writing (do this first)
excludeNopaths to leave untouched (runtime-driven elements)
minSizeNoadd 44×44 UISizeConstraint to buttons
aspectRatioNoadd UIAspectRatioConstraint at current aspect
referenceResolutionNouiscale mode design res (default 1280×720)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • changedInput schema / properties / mode / description
      Previous value: -"default scale"New value: +"Conversion mode (see the description). Default scale."
    • addedInput schema / properties / path / description
      Added value: +"Root of the UI to convert, e.g. \"StarterGui.HUD.Panel\". Dot path from the DataModel root, e.g. \"Workspace.Map.Door\" or \"StarterGui.HUD.Frame\". A leading \"game.\" is optional; a duplicate sibling name takes the suffix Tufan prints, e.g. \"Part (2)\"."
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false; the description adds real substance beyond them: the exact properties rewritten, the per-axis validation formula, the skip rule for runtime-driven elements, and a required dryRun preview. It still doesn't state outright that original Offset values are lost after a write (only implied by the existence of the reverse `offset` mode).

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?

Front-loaded with the core action, then a mode list, then flags — dense but every clause carries operational information (property list, formula, skip rule, safety practice). No filler or restatement of the tool name.

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 destructive 8-parameter mutation with a nested referenceResolution object and no output schema, the description covers transformation scope, mode selection, safety workflow, and protection logic. What it omits is what a dryRun preview reports back and how per-property failures are surfaced, which an agent would need to interpret results.

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 coverage is 100%, so the baseline is 3, but the description earns more: the `mode` enum's schema text merely says 'see the description', and the description is where the four modes are actually defined. It also spells out what `aspectRatio` and `minSize` inject (UIAspectRatioConstraint at current aspect; 44×44 UISizeConstraint on buttons) and notes that layout-managed kids are skipped.

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 — converts Offset→Scale across a named set of UI properties on a subtree — so the agent knows exactly what transformation this performs. It does not explicitly name the read-only diagnostic sibling (scan_responsive), so sibling differentiation is left to inference.

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

Usage Guidelines4/5

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

Gives a concrete usage rule ('ALWAYS dryRun first to preview'), explains each of the four modes with what it is for (scale, offset/reverse, fit, uiscale), and says runtime-driven elements are skipped so draggable/resizable panels are never broken. It stops short of naming an alternative tool for a pure audit, but the when-to-use context is clear.

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