Skip to main content
Glama
Roblox Studio MCP Gateway

Roblox Studio MCP Gateway

by camilin7483

roblox_capture

Capture Roblox Studio scene, memory, script, or micro profiles over a set duration to diagnose performance and runtime issues.

Instructions

scene | memory | script-profiler | micro-profiler.

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

Input Schema

NameRequiredDescriptionDefault
kindNoscene
secondsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

D1.5/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses nothing: not whether captures pause or slow the place, whether profilers have runtime overhead, how long a 'seconds' capture blocks, or what the output schema contains per kind.

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

Conciseness2/5

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

It is short, but the brevity is under-specification rather than conciseness: four bare tokens separated by pipes with no sentence, no front-loaded purpose, and no framing to tell the reader these are parameter options.

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

Completeness1/5

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

An output schema exists, but for a capture/profiling tool with two undocumented parameters and zero annotations, an agent still cannot tell what each kind does, how long it runs, or what side effects to expect. The definition is far too thin for the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description's only contribution is implying the four valid `kind` values, with no defaults, format, or casing guidance. The `seconds` parameter is not addressed at all, leaving a required explanation missing for both parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is only a pipe-delimited list of four tokens that appear to be the accepted values for the `kind` parameter; it never states a verb or says what is actually captured. An agent can guess this is a capture/profiling tool from the name, but the description itself only restates the name rather than defining the operation.

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

Usage Guidelines1/5

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

There is no guidance on when to choose scene vs memory vs script-profiler vs micro-profiler, no mention of cost, duration, or side effects, and no routing to alternatives such as roblox_profile or roblox_status.

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