Skip to main content
Glama
Roblox Studio MCP Gateway

Roblox Studio MCP Gateway

by camilin7483

roblox_selection

Retrieve the current Roblox Studio selection, or set it by passing instance paths. Use it to inspect or change what is selected before editing or running playtests.

Instructions

Get selection, or set it when paths are given.

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

Input Schema

NameRequiredDescriptionDefault
pathsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and does not meet it. It never states that setting the selection replaces the current Studio selection, whether it requires an open place/session, whether paths must already exist, or what an empty array does. Only the get/set switch is disclosed.

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 front-loaded sentence with no filler, and the get case is stated before the set case. It is arguably too terse for a dual-mode tool, but there is no wasted wording to cut.

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

Completeness2/5

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

The presence of an output schema relieves the description of explaining return values, and it does cover the core get/set duality. For a tool that mutates Studio editor state with zero annotation coverage and an entirely undocumented parameter, the description leaves too many operational questions (path format, replacement semantics, session requirements) unanswered.

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 0% and the single parameter 'paths' is documented only by its title and a null default. The description does add real meaning by establishing that this parameter flips the tool into write mode, which the schema does not convey. However, it never explains the expected path format (array of what? instance paths, names?), whether an empty array clears the selection, or what invalid entries do.

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 specific pair of verbs on a specific resource (get the selection, set the selection) and names the condition that switches between them ('when paths are given'). An agent can tell what the tool does at a glance, though 'selection' and 'paths' are only meaningful if the agent already knows Roblox Studio terminology.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The mode condition ('when paths are given') implicitly tells the agent how to choose between get and set, which is useful. But there is no guidance on when to use this versus the other ~30 Studio tools, no prerequisites (e.g. an active Studio connection), and no note on what happens with an empty or invalid path list.

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