Skip to main content
Glama
Roblox Studio MCP Gateway

Roblox Studio MCP Gateway

by camilin7483

roblox_input

Simulate mouse clicks and keyboard presses in Roblox Studio to test controls and automate playtest input.

Instructions

Simulate mouse/keyboard input 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": "roblox_input"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
keyNo
kindNomouse
actionNoclick

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.6/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 burden of behavioral disclosure but says almost nothing beyond the one-line purpose. It does not explain whether input is sent to the active Studio window, whether coordinates are viewport-relative, whether actions are reversible, or what connection state is required.

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

Conciseness3/5

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

The single sentence is front-loaded and free of waste, but it is under-specified rather than concise. Brevity here costs needed behavioral and parameter context.

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 explained. However, for a five-parameter interaction tool with no annotations and no schema descriptions, the definition is far too thin to let an agent call it correctly without guessing parameter semantics and preconditions.

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% across five parameters, and the description does not map any of them. The words 'mouse/keyboard' hint at x/y versus key usage, but the meanings of x, y, key, kind, and action remain undocumented in both schema and description.

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 uses a specific verb ('Simulate') and resource ('mouse/keyboard input') scoped to Studio, so the agent can tell this tool issues synthetic input events. It does not differentiate from siblings like roblox_playtest or roblox_multiplayer, but the core purpose is clear.

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 guidance on when to use this tool versus alternatives such as roblox_playtest or roblox_exec, nor any stated preconditions (e.g., Studio must be focused or a playtest must be running). The agent must infer usage entirely.

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