Skip to main content
Glama
Sign In
Roblox Executor MCP Server

Roblox Executor MCP Server

by okenjioxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List GC threads

list-gc-threads
Read-onlyIdempotent

Enumerate thread objects from getgc(true), with coroutine status when available, for inspecting live Roblox runtime threads.

Instructions

Enumerate thread objects from getgc(true), including coroutine status where available. Signature: { limit: any?, threadContext: number? }. Phase: observe; cost=medium; idempotency=read-only. Requires: active-client. Capabilities: getgc. Produces: bounded-candidates, structured-observation. Safety: read-only. On failure: inspect tool-schema for exact fields, defaults, constraints, and an invocation example.

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-gc-threads"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoOptional hard result/work budget used to keep output and runtime bounded.
threadContextNoOptional Roblox thread identity for this call; omit it to use the server default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0-spies.2

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so the safety profile is covered. The description adds genuine context beyond that: the active-client prerequisite, cost=medium, and the bounded-candidates / structured-observation output characteristics. No contradiction with annotations.

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 purpose, then compact metadata tags. Efficient overall, though the signature and Safety: read-only lines partly duplicate structured data (schema and annotations), which is slight redundancy rather than bloat.

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 read-only, no-output-schema tool, the definition covers prerequisites, cost, phase, and failure handling (inspect tool-schema). Nothing critical is missing, though a brief note on pagination/bounding behavior of the limit budget would make it fully self-sufficient.

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%, so both parameters are already fully documented in the schema. The signature line ({ limit: any?, threadContext: number? }) merely restates what the schema provides and adds no extra syntax or default meaning, so the baseline 3 applies.

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 verb (Enumerate) and resource (thread objects from getgc(true)), and even notes the coroutine-status enrichment. This clearly distinguishes it from close siblings like list-gc-tables, list-gc-functions, and list-registry-objects without opening their schemas.

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?

Provides prerequisites (Requires: active-client) and a phase (observe), which gives implied usage context. However, it never names an alternative tool or states when NOT to use this versus filter-gc or search-gc-value, leaving selection to inference.

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

Deploy Server

Other Tools