Skip to main content
Glama

list_places

Read-only

Lists Roblox Studio places currently connected to the bridge, including placeId, name, gameId, and project folder, so you can choose the right place for other tool calls.

Instructions

List the Roblox Studio places connected to the bridge right now, with placeId, name, gameId and project folder. Read-only. Call it first when several places are open, then pass a placeId or name as the place argument of other tools; with one place open, tools target it automatically. To check a single connection, ping is enough.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/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, and the description reinforces read-only as a one-word statement. Beyond that it discloses live/current-state semantics ('connected ... right now') and the side-effect-free auto-targeting behavior when only one place is open, which the annotations do not convey. It stops short of noting instability of the list (connections dropping between calls) or whether stale/disconnected places appear.

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?

Four short sentences, front-loaded with what it returns, then safety, then workflow, then the cheaper alternative. No filler or restated title.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-parameter, read-only discovery tool with no output schema, the description supplies everything needed: the returned fields, the state it reflects, and how to use the result downstream. Nothing an agent needs to invoke it correctly is missing.

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?

Zero parameters, so the baseline is 4. The description correctly frames it as taking no arguments while clarifying that the placeId/name it returns is the input other tools consume, which is meaningful orientation even with an empty schema.

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?

Names a specific verb and resource ('List the Roblox Studio places connected to the bridge') and pins the scope with 'right now', then enumerates the returned fields (placeId, name, gameId, project folder). It is immediately distinguishable from snapshot, plugin, and log listing 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 explicit sequencing ('call it first when several places are open'), explains what to do with the result (pass placeId or name as the place argument of other tools), states the degenerate case (one place open = automatic targeting), and names the cheaper alternative for a different need ('to check a single connection, ping is enough').

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