Skip to main content
Glama
Sign In
Roblox MCP

Roblox MCP

by sdhzcxnb0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

studio_status

Verify Roblox Studio plugin connection status and report the open place, port, and queue state.

Instructions

Check whether the Roblox Studio plugin is connected and report the open place, port and queue state.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description must carry the full behavioral burden. It discloses that the tool reports connection status, open place, port, and queue state, implying a read-only diagnostic. It does not explain behavior when the plugin is disconnected, whether it errors or returns an offline status, or the shape of the reported data.

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?

The description is a single front-loaded sentence with no filler. It states the core check first and then lists the reported fields efficiently.

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?

For a zero-parameter status tool, the description is largely complete: it names the connection check and the reported state fields. The main missing piece is failure/disconnected behavior and return format, but the low complexity keeps this from being a serious gap.

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 there is no parameter semantics to clarify. The baseline for zero-parameter tools is 4, and the description appropriately does not waste space documenting nonexistent inputs.

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?

The description states a specific action (check and report) and specific resources (plugin connection, open place, port, queue state). It clearly distinguishes this diagnostic/status tool from sibling tools like read_script, get_selection, and execute_luau.

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

Usage Guidelines3/5

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

Usage is implied: this is a status/diagnostic check for the Studio plugin. However, there is no explicit guidance about when to use it versus other tools or what conditions might make it appropriate, such as checking before running scripts.

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