Skip to main content
Glama

game_overview

Get a one-call architectural overview of a Roblox place: PlaceId, services with script and child counts, all Remotes and Bindables, CollectionService tags, plus Lighting and StarterPlayer settings.

Instructions

One-call architectural overview of the place: PlaceId, services with script/child counts, all Remotes & Bindables, all CollectionService tags, Lighting & StarterPlayer settings.

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

Input Schema

NameRequiredDescriptionDefault
studioNoOptional. Target Studio (name substring, place id or id). Only needed when several Studios are open and none was selected.
contextNoDatamodel to run in. Default: edit when not playing, otherwise server.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden and only partially discharges it: it lists what gets returned (implying a read-only snapshot) but says nothing about response size, cost, whether it works during play, or whether it affects the session. The enumerated payload does convey scope, but for an unannotated tool the omission of read-only/cost/context behavior is a real gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence, front-loaded with the key framing ("one-call architectural overview") followed by the payload list. No filler, though the enumeration is a comma run-on that could be grouped more scannably.

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?

No output schema exists, so the description must convey return content — and it does, enumerating the major sections the agent will get back. What is missing is any sense of the returned shape's structure or size, and nothing addresses behavior during a live play session even though context includes client/server.

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 both parameters (studio, context) are fully documented in the schema including the default-resolution rule for context. The description adds nothing beyond the schema, so the 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 specific capability — a single-call architectural overview — and enumerates exactly what it covers (PlaceId, services with script/child counts, Remotes & Bindables, CollectionService tags, Lighting & StarterPlayer). An agent can tell this is an aggregate read of the whole place rather than a targeted query. It stops short of naming which sibling to prefer for narrower questions (tree, inspect, script_grep).

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 only implied by the phrase "one-call architectural overview," which suggests it is the cheap way to get broad context before drilling in. There is no explicit when-to-use, when-not, or guidance about using tree/inspect/script_grep instead for a narrower slice. The agent must infer the triage role from wording alone.

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