Skip to main content
Glama
Roblox Studio MCP Gateway

Roblox Studio MCP Gateway

by camilin7483

roblox_network

Configures the playtest network profile via Luau, letting you simulate network conditions during Roblox Studio playtests.

Instructions

Set playtest network profile via Luau.

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

Input Schema

NameRequiredDescriptionDefault
profileNodefault

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.4/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 delivers almost nothing. 'Set' implies mutation, but it does not state what state is changed, whether the change persists across sessions, whether it affects an in-flight playtest, whether permissions are needed, or how to revert. Only the bare implication of a write operation is conveyed.

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?

It is a single short sentence with no padding, which is structurally clean, but brevity here is under-specification rather than economy: six words to describe a mutation tool with an undocumented enum-like parameter. 'via Luau' consumes space without clarifying anything.

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, but for a mutating configuration tool with zero annotations and an opaque parameter, the description is far too thin. An agent cannot tell what profiles are valid, what the default means, or what side effects to expect before calling it.

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% for the single 'profile' parameter, which has a 'default' default but no documented allowed values. The description's phrase 'network profile' only echoes the parameter name and adds no semantics such as valid profile identifiers or the effect of each. With coverage this low the description should compensate, and it does not.

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

Purpose3/5

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

The description pairs a verb ('Set') with a resource ('playtest network profile'), so the general intent is recoverable. But 'network profile' is never defined — no hint of what dimension is being configured (latency, bandwidth, packet loss?) — and nothing distinguishes this from siblings like roblox_playtest, roblox_multiplayer, roblox_device, or roblox_profile. The trailing 'via Luau' is unexplained jargon.

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 guidance, no prerequisites, and no mention of alternatives. The phrase 'playtest network profile' weakly implies this belongs to playtest setup, but the agent must guess whether it applies before, during, or after a session, and whether it replaces or supplements roblox_playtest settings.

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