Skip to main content
Glama

is_running

Read-only

Check whether a simulation is running in Roblox Studio—Play, Run, or edit mode—so you can verify edit mode before mutating. Read-only state check; start or stop sessions with Studio's official MCP.

Instructions

Whether a simulation is running in the target Studio: a Play session, Run mode, or plain edit mode. Read-only state check — use it to confirm you're in edit mode before mutating. To START/STOP a play session or send input, use Roblox's official Studio MCP.

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

Input Schema

NameRequiredDescriptionDefault
placeNoTarget place (PlaceId or project name). Defaults to the bound/sole connected place.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is largely covered; the description reinforces this with 'Read-only state check.' It adds genuine behavioral context beyond the annotations by enumerating the three states the tool distinguishes (Play session, Run mode, plain edit mode), but does not say what the tool actually returns (boolean vs. mode label) or how it behaves if no place is connected.

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?

Two sentences, front-loaded with the core question and immediately followed by the routing advice. No filler, no restatement of the title, and the negative guidance is compressed into a single clause.

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-required-parameter read-only check with a fully documented schema, this is nearly complete. The one gap is the absence of an output schema combined with no statement of the return value — the agent learns which states exist but not what the response looks like (a boolean, a mode string, or an object).

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?

Schema description coverage is 100%, and the schema itself documents that place accepts a PlaceId or project name and defaults to the bound/sole connected place. The description only refers to 'the target Studio' generically, adding no syntax or defaulting detail beyond the schema. Baseline 3 is appropriate.

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?

States a specific predicate with its subject and enumerated scope: whether a simulation is running in the target Studio, covering Play session, Run mode, and plain edit mode. An agent can immediately tell this is a state query rather than a control action, distinguishing it from start/stop siblings.

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

Usage Guidelines5/5

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

Gives an explicit use case ('use it to confirm you're in edit mode before mutating') and an explicit exclusion with the alternative named ('To START/STOP a play session or send input, use Roblox's official Studio MCP'). Both the when and the when-not are covered.

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