Skip to main content
Glama
Roblox Studio MCP Gateway

Roblox Studio MCP Gateway

by camilin7483

roblox_status

Check whether the Roblox Studio bridge and plugin are connected, and retrieve the effective environment configuration to diagnose setup or connection issues.

Instructions

Bridge + plugin status and effective env config.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/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 burden, and it discloses almost nothing beyond the topic — no statement that it is read-only, no auth/connection requirements, no note about whether it fails when the plugin is absent. 'Status' weakly implies a passive check, but that is inference, not disclosure.

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 telegraphic fragment with no filler, which is front-loaded, but the compression crosses into under-specification — 'Bridge +' reads like shorthand note rather than a sentence an agent can act on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 needn't be spelled out, and there are no parameters to document, which lowers the bar considerably. Still, the complexity that remains — what a bridge/plugin status is and what calling it presupposes — is entirely undisclosed.

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 compensate for; baseline for a 0-param tool is 4. No usable details are lost here.

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 names two resources ('Bridge + plugin status' and 'effective env config') and implies a read of current state, but 'Bridge' is unexplained jargon and the phrase is too compressed to say concretely what is reported back. An agent can guess this is a status/probe call, but not confidently distinguish it from siblings like roblox_ensure_ready.

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 at all: no mention of prerequisites (does a bridge/plugin need to be connected first?), no indication of when this should be preferred over roblox_ensure_ready or roblox_device, and no exclusions. The agent must infer call conditions purely from the name.

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