Skip to main content
Glama
Roblox Studio MCP Gateway

Roblox Studio MCP Gateway

by camilin7483

roblox_device

Read or set the simulated device state in Roblox Studio playtests, letting you switch or inspect the emulated device before diagnosing runtime behavior.

Instructions

Device simulator state/set.

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_device"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNostate
deviceNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

D1.8/5.0
Behavior2/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 and mostly fails it. The 'state/set' phrasing hints that the tool both reads and mutates simulator state, giving some sense of a write path, but there is no information on required setup, whether changes persist across sessions, or side effects on a running playtest.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four words are technically concise but the result is under-specification rather than economy. There is no structure at all: no statement of the operation, no parameter explanation, and nothing front-loaded beyond a vague noun phrase.

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?

An output schema exists, so return values need not be described, but a tool with zero schema coverage and zero annotations needs the description to supply parameter and behavior context, which it does not. For a two-parameter simulator-control tool this leaves the agent without enough to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so both parameters (action, defaulting to 'state', and device, defaulting to empty) are undocumented anywhere. The description hints that 'action' has at least state and set values but never spells out the accepted values or what 'device' should contain, leaving the caller to guess.

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

Purpose2/5

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

"Device simulator state/set" gestures at reading and setting emulated device state, but is closer to a restatement of the name than a real definition. It never says what 'device' means in this context (emulated mobile/console profile, resolution, input model) or what 'state' is, so an agent cannot distinguish it from roblox_input or roblox_status beyond guessing.

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

Usage Guidelines1/5

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

No when-to-use guidance, no prerequisites, and no mention of an alternative such as roblox_input for injecting input or roblox_status for environment checks. The only hint is the word 'set', which implies mutation for some action values, with no conditions attached.

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