Skip to main content
Glama

set_attribute

DestructiveIdempotent

Create or overwrite a single attribute on one Roblox Studio instance as one undo step. Accepts primitives or typed wrappers like Vector3, Color3, UDim2, and CFrame.

Instructions

Create or overwrite one attribute on one instance, recorded as one Studio undo step. For several attributes use mass_set_attribute; for built-in properties use set_property.

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": "<name>",
      "value": "<value>"
    },
    "name": "set_attribute"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesAttribute name. Letters, digits and underscores, up to 100 characters (a Roblox rule).
pathYesInstance 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)".
placeNoTarget place (PlaceId or project name). Defaults to the bound/sole connected place.
valueYesAttribute 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"}.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.1
    • addedInput schema / properties / name / description
      Added value: +"Attribute name. Letters, digits and underscores, up to 100 characters (a Roblox rule)."
    • addedInput schema / 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 / value / description
      Added value: +"Attribute 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

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the mutation profile is covered structurally. The description adds genuinely new behavior: overwrite semantics and the fact that the write is a single Studio undo step, which matters for rollback expectations. It does not discuss failure modes (missing instance, invalid name) or permission requirements, keeping it below a 5.

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?

Two tight sentences with the core action front-loaded and the alternative routing second; nothing is redundant. Slightly dense phrasing ('recorded as one Studio undo step' as a clause) but well organized.

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 4-parameter mutation tool with a rich schema and four annotation hints, the description covers purpose, alternatives, overwrite behavior and undo granularity. No output schema exists, but the return value is trivial for a setter, so the lack of return description is a minor gap rather than a blocker.

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 the schema itself documents name/path/place/value with concrete examples and typed wrapper syntax. The description adds no parameter-level meaning beyond what is already there, so the baseline 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 ('Create or overwrite one attribute on one instance') plus a distinguishing scope ('one'), and explicitly names the sibling that handles the many-attribute case. An agent can tell it apart from mass_set_attribute and set_property without opening any schema.

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 explicit routing: several attributes -> mass_set_attribute, built-in properties -> set_property. The remaining case (one custom attribute) is precisely this tool, so the when-to-use boundary is fully determined.

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