Skip to main content
Glama

set_selection

Idempotent

Replace the current Roblox Studio selection with specified instance paths to target objects or prepare for a Studio command, while leaving instances unchanged and skipping unresolved paths.

Instructions

Replace the user's Studio selection with the given instances, to point them at something or prepare for a Studio command. Changes only the selection, never the instances. Paths that do not resolve are skipped; the reply says how many were selected. An empty list clears the selection.

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": {
      "paths": "<paths>"
    },
    "name": "set_selection"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathsYesDot paths to select, e.g. ["Workspace.Map.Door", "Workspace.Map.Window"].
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 / paths / description
      Added value: +"Dot paths to select, e.g. [\"Workspace.Map.Door\", \"Workspace.Map.Window\"]."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint=false, idempotentHint=true), the description discloses non-obvious behavior: unresolvable paths are silently skipped rather than erroring, and the reply reports the count selected. Since there is no output schema, that reply note is the agent's only expectation of the return value.

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?

Four short sentences, front-loaded with the action and its scope boundary, then the failure mode, then the return behavior. 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.

Completeness5/5

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

For a two-parameter, non-destructive setter, the description covers action, scope limit, invalid-input handling, and response content. The only thing not described, the default for 'place', is already spelled out in the schema.

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; the description earns an extra point by explaining edge semantics the schema does not — that an empty paths list clears the selection and that invalid paths are skipped rather than rejected. The 'place' parameter is left entirely to the schema, which is acceptable given full coverage.

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?

The description names a specific verb and resource ('Replace the user's Studio selection with the given instances') and immediately bounds the effect with 'Changes only the selection, never the instances', which separates it from mutation siblings such as set_property or set_attribute.

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?

It gives two concrete use cases ('point them at something or prepare for a Studio command') and documents a special case ('An empty list clears the selection'). It stops short of naming the read counterpart get_selection or stating when not to use it, so routing is implied rather than explicit.

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