Skip to main content
Glama

project_health

Read-only

Get a read-only overview of a Roblox place: instance, script, and part counts, Luau size, particles, lights, tags, service breakdown, and StreamingEnabled before deeper analysis.

Instructions

One-look census of the game (installed plugins and Studio UI excluded): instance / script / part counts, total Luau size, particle + light counts, a per-service descendant breakdown, tag count, and StreamingEnabled. The fast 'what is this game?' overview before diving in. Read-only. For performance problems use scan_perf; for security use scan_backdoors; to explore the hierarchy use get_tree.

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

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.2/5.0
Behavior3/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's 'Read-only' merely restates that. The genuinely additive behavior is the exclusion rule (installed plugins and Studio UI are not counted), which prevents misreading the counts, but return shape, cost on large places, and truncation behavior are unaddressed.

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?

Front-loaded with the core definition, then routing guidance, with no filler sentences. The long enumeration of counted metrics is dense but each item informs selection; it could be grouped slightly more tightly but nothing is wasted.

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 read-only census with no output schema, the description effectively describes the payload by listing every reported metric, so an agent knows what will come back. Zero required parameters and a trivially documented optional parameter leave no gaps.

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 single optional 'place' parameter is fully documented in the schema as PlaceId or project name with a bound-place default. The description adds nothing about it, so the baseline 3 applies rather than a penalty.

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?

The description names a specific verb-and-resource pair ('census of the game') and then enumerates exactly what is measured: instance/script/part counts, total Luau size, particle and light counts, per-service descendant breakdown, tag count, StreamingEnabled. It also explicitly scopes out installed plugins and Studio UI, which an agent could not have guessed.

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?

It states the intended moment of use ('the fast "what is this game?" overview before diving in') and routes three alternatives by intent: scan_perf for performance, scan_backdoors for security, get_tree for hierarchy exploration. Exclusions and alternatives are both explicit.

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