Skip to main content
Glama

studio_select

Sets the active open Roblox Studio instance for all following calls when several are open, identified by name substring, place ID, or status ID.

Instructions

Choose which open Studio instance all following calls target (only needed when several are open).

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": {
      "studio": "<studio>"
    },
    "name": "studio_select"
  }
}

Input Schema

NameRequiredDescriptionDefault
studioYesName substring, place id, or id from studio_status.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose key statefulness — the choice persists for all following calls — but says nothing about how ambiguous name substrings are resolved, whether an invalid studio errors, or how long the selection lasts.

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?

One sentence with the core behavior front-loaded and the necessity condition placed as a compact parenthetical. There is no redundant or filler wording.

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?

With a single required parameter, no output schema, and no annotations, the description covers purpose, scope, and necessity well. Only the failure/ambiguity behavior for the selection is left unstated.

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 100% and the schema already enumerates the accepted forms (name substring, place id, or id from studio_status). The description adds no format, matching, or precedence details 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.

Purpose5/5

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

Uses a specific verb ('Choose') plus the resource ('which open Studio instance') and states the downstream scope ('all following calls target'). The parenthetical makes clear it is a targeting/selection tool, distinct from sibling tools like studio_status that report state.

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?

Explicitly states when it is required ('only needed when several are open'), which also implies the when-not case (a single open instance needs no selection). It does not name a sibling alternative, though the parameter description points to studio_status for IDs.

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