Skip to main content
Glama

scan_responsive

Read-only

Audit a Roblox UI subtree for resolution breakage: flags offset-locked properties, sub-44px tap targets, and runtime pixel positioning in scripts. Read-only; run before make_responsive and after to confirm fixes.

Instructions

Audit a UI subtree for what breaks on other resolutions — across the tree AND the scripts. Flags Offset-locked Position/Size/CanvasSize/CellSize/CellPadding/Padding/CornerRadius, sub-44 tap targets, and runtime pixel-positioning in code. Recognizes intentional draggable/resizable elements (tagged) and instead checks their drag logic (clamps to viewport?). Read-only. Run it before make_responsive to see what needs fixing, and again after to confirm.

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": "scan_responsive"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesRoot of the UI to audit, e.g. "StarterGui.HUD". 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • addedInput schema / properties / path / description
      Added value: +"Root of the UI to audit, e.g. \"StarterGui.HUD\". 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.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description restates 'Read-only' redundantly but harmlessly. Beyond that it discloses real behavior: it inspects scripts as well as the instance tree, recognizes tagged draggable/resizable elements and instead validates their drag logic (viewport clamping). It stops short of describing traversal limits, cost on large trees, or how findings are reported.

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, then detection scope, then workflow — a sensible order with no filler sentences. Slightly dense in the enumeration, and 'Read-only' duplicates the readOnlyHint annotation rather than adding information.

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

Completeness5/5

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

For a two-parameter read-only audit with no output schema, the description covers what is checked, that scripts are included, the special handling of tagged interactive elements, safety posture, and when to invoke it. The only unstated item is the shape of the findings, which 'Flags ...' adequately implies.

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 coverage is 100% and both parameters carry detailed descriptions (dot-path format, optional 'game.' prefix, duplicate-name suffix, place default). The description adds no parameter-level meaning, so the baseline of 3 applies.

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?

States a specific verb and resource ('Audit a UI subtree for what breaks on other resolutions') and enumerates exactly what it detects: offset-locked properties, sub-44 tap targets, and runtime pixel positioning. The scope note 'across the tree AND the scripts' separates it from a tree-only check, and the make_responsive reference anchors it against a sibling.

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?

Gives an explicit workflow: run before make_responsive to see what needs fixing, and again after to confirm. That is both a when-to-use and a relationship to the alternative sibling, leaving nothing to infer about sequencing.

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