Skip to main content
Glama

mass_set_attribute

DestructiveIdempotent

Set multiple attributes across many Roblox instances in one call, recorded as a single Studio undo step. Failed edits are reported individually while the rest still apply.

Instructions

Set many attributes, across any number of instances, in one call recorded as one Studio undo step. Each edit is tried on its own; failures are listed with their index and reason while the rest still apply. The attribute version of mass_edit; for one attribute set_attribute is enough.

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": {
      "edits": "<edits>"
    },
    "name": "mass_set_attribute"
  }
}

Input Schema

NameRequiredDescriptionDefault
editsYesOne entry per change. The same path may appear several times.
placeNoTarget place (PlaceId or project name). Defaults to the bound/sole connected place.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.1
    • addedInput schema / properties / edits / description
      Added value: +"One entry per change. The same path may appear several times."
    • addedInput schema / properties / edits / items / properties / name / description
      Added value: +"Attribute name"
    • addedInput schema / properties / edits / items / properties / path / description
      Added value: +"Instance to change. 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)\"."
    • addedInput schema / properties / edits / items / properties / value / description
      Added value: +"New value. Write a primitive (string, number, boolean) or a typed wrapper: {Vector3:[x,y,z]}, {Color3:[r,g,b]} (0-1), {UDim2:[xScale,xOffset,yScale,yOffset]}, {CFrame:[x,y,z] or all 12 components}, {EnumItem:\"Enum.Material.Wood\"}, {BrickColor:\"Bright red\"}."
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description usefully adds that all edits collapse into one Studio undo step and that each edit is attempted independently with failures reported by index and reason. It does not say whether attributes are created when absent, whether instance-not-found is a failure or a skip, or that existing attribute values are overwritten, which is the concrete meaning of the destructive hint.

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?

Three short sentences, front-loaded with what the tool does, then failure semantics, then sibling routing. No filler, no restatement of the name or title.

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 two-parameter batch mutation with a rich schema but no output schema, the description covers the undo grouping and the shape of the result surface (per-index failures with reasons). The remaining gap is what happens on missing instances or missing attributes, which matters for a destructive batch operation.

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 100%, with the path syntax, duplicate-sibling suffix convention, and value wrapper formats all documented in the schema itself. The description adds no parameter-level meaning beyond noting multiple instances and index-based failure reporting; the baseline for full coverage is 3, and nothing here exceeds what the schema supplies.

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 (Set), resource (attributes), and scope (many, across any number of instances) with the added framing of a single undo step. It also names exactly which siblings it is and is not: the attribute counterpart of mass_edit, versus set_attribute for a single edit.

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 clear routing rule: use set_attribute when changing one attribute, use this tool for many. It also implies parity with mass_edit for the attribute domain. It stops short of stating exclusions, such as when batching attribute writes is a bad idea or how this differs from mass_edit on properties.

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