Skip to main content
Glama

selection

Retrieve the instances currently selected in Roblox Studio so coding agents can act on them, or set the selection programmatically to target specific paths before running edits.

Instructions

Get the instances the user currently has selected in Studio (great for 'fix this'), or set the selection.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "selection"
  }
}

Input Schema

NameRequiredDescriptionDefault
setNoPaths to select. Omit to just read the selection.
studioNoOptional. Target Studio (name substring, place id or id). Only needed when several Studios are open and none was selected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It discloses the two modes (read vs. set) and that setting mutates the user's editor state, but does not say whether setting replaces or extends the existing selection, what happens with no Studio open, or what the read returns. Key side-effect details are left in the schema's parameter text or unstated.

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?

A single tight sentence with the primary use case front-loaded and the alternate mode appended. The parenthetical earns its place by giving a concrete trigger, though cramming both modes into one clause makes the write path slightly abrupt.

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

Completeness3/5

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

For a 2-parameter, no-required-input tool with no output schema, it covers both modes and defers argument detail to the schema. It is still thin on the mutation path — replacement semantics, no-selection case, and failure behavior with zero Studios open are absent.

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%, including the meaningful note that omitting `set` just reads the selection and that `studio` matters only with multiple open Studios. The description adds no parameter meaning beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb+resource pair: reading the instances currently selected in Studio, plus the inverse write mode "or set the selection." An agent immediately knows it deals with Studio selection state, though the dual read/write nature is only implied by the trailing clause rather than structured explicitly.

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?

"great for 'fix this'" gives a real, concrete usage context — invoke it when the user refers to something they already have selected. It does not state when not to use it or name an alternative for the set-selection case, so it falls short of a 5.

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