Skip to main content
Glama

studio_status

Check connected Roblox Studio instances, the targeted session, play mode, datamodels, PlaceId, script-sync state, and recent sync activity in one call.

Instructions

START HERE. One call shows: connected Studio instances (and which one is targeted), play mode, available datamodels, PlaceId, script-sync state and recent sync activity.

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
studioNoOptional. Target Studio (name substring, place id or id). Only needed when several Studios are open and none was selected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it implies a read-only snapshot by describing what is 'shown' and covers recent sync activity, but never states side-effect profile, what happens when no Studio is connected, or that the result may be stale. The field enumeration does meaningful work that the missing annotations would otherwise have to cover.

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?

A single sentence plus a front-loaded imperative; every clause names a distinct piece of returned state with no filler, and the call-to-action leads.

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?

With no output schema, the description compensates by enumerating the returned fields, which is the essential information for a status tool, and the single parameter is fully documented in the schema. It omits failure modes (no Studio open, ambiguous target), which is the only remaining gap.

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

Parameters3/5

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

The description adds nothing about the optional 'studio' parameter, but schema description coverage is 100% and the schema itself explains the substring/place-id/id forms and when targeting is needed. Baseline 3 applies.

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 names a concrete resource and enumerates exactly what the snapshot contains (instances, targeted instance, play mode, datamodels, PlaceId, sync state, recent activity), so the agent knows precisely what comes back. It does not explicitly contrast with nearby tools like sync_status or instance, which keeps it from a 5.

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

Usage Guidelines4/5

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

'START HERE' gives a clear directive to call this before other tools, and 'One call shows' implies it can replace several narrower queries. There is no explicit when-not guidance or named alternative, so it stops short of 5.

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