Skip to main content
Glama

get_attributes

Read-only

Reads all attributes set on a Roblox instance as a JSON name-to-value object, returning {} when none exist. Use it to inspect attribute data without changes.

Instructions

Read every attribute set on one instance as a JSON object of name to value. Read-only; returns {} when there are none. For attributes together with properties, tags and children use describe.

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

Input Schema

NameRequiredDescriptionDefault
pathYesInstance to read. 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: +"Instance to read. 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, so the description doesn't need to re-argue safety. It adds real value beyond them by disclosing the return shape and the empty-case behavior ("returns {} when there are none"), which matters because there is no output schema. It stops short of saying how non-primitive Roblox attribute types are serialized or what happens on a bad path.

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 with the return contract front-loaded, then the empty case, then the routing hint. No redundant restatement of the tool name or annotations.

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 read tool with no output schema, the description covers purpose, return shape, empty result, and sibling routing — enough to call it correctly. Minor gaps remain around error behavior for an unresolvable path and conversion of non-JSON-native attribute value types.

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 description coverage is 100%, and the schema already explains the dot-path format, optional "game." prefix, and duplicate-name suffix convention. The description adds no parameter guidance beyond what the schema carries, 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 ("Read every attribute set on one instance") plus the exact return shape ("a JSON object of name to value"). This lets an agent distinguish it from get_properties and the broader describe 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?

Explicitly routes the agent to the alternative: "For attributes together with properties, tags and children use describe." The condition that selects the sibling is named outright, and the narrow single-purpose nature of this tool is implied by contrast.

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