Skip to main content
Glama
Sign In
Roblox MCP

Roblox MCP

by sdhzcxnb0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_selection

Retrieves the objects currently selected in Roblox Studio so an AI client can inspect and act on the user's active selection.

Instructions

Show what the user currently has selected in Studio.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. "Show" implies a non-mutating read and "currently" implies a live snapshot, but it does not state whether the call is read-only, what happens when nothing is selected, whether multiple objects can be selected, or what shape the selection takes.

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 short sentence with the key qualifier ("currently") front-loaded and no wasted words. It is appropriately sized, though the brevity contributes to the missing usage and return-shape context.

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?

The tool is simple and takes no arguments, so the core definition is adequate. However, with no annotations and no output schema, the description should say more about what a "selection" contains and how an empty selection is represented; those gaps matter for correct interpretation of the result.

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?

The tool takes zero parameters, so the baseline is 4. There is nothing parameter-related for the description to clarify or omit.

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?

The description gives a specific verb ("Show") and a specific resource ("what the user currently has selected in Studio"), which is distinct from siblings like get_tree or get_instance. It does not explicitly name how it differs from those tools, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no alternative is named. The phrase "currently has selected" implies a live-state lookup, but an agent must infer that on its own rather than being routed to get_instance or get_tree when appropriate.

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

Deploy Server

Other Tools