Skip to main content
Glama
Roblox Studio MCP Gateway

Roblox Studio MCP Gateway

by camilin7483

roblox_profile

Flags profiler readings that exceed microsecond or memory budgets, helping diagnose performance issues during Roblox Studio playtests.

Instructions

Flag profiler readings over budget.

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_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
micro_sNo
memory_mbNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden and falls well short: it does not say whether flagging is a read-only evaluation or a mutation, whether it throws, logs, or emits readings into the output, nor whether results persist. The word 'budget' implies comparison against a threshold whose source is never stated.

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

Conciseness3/5

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

The single sentence is front-loaded and free of padding, but it is terse to the point of under-specification rather than efficient. Brevity here costs clarity instead of buying it.

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

Completeness3/5

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

An output schema exists, so return values need not be described, which relieves some burden. For a two-parameter diagnostic tool with no annotations, though, the definition leaves the core semantic question — thresholds vs. readings — unresolved, so it is only minimally adequate.

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%, so the description must compensate and does not: it never mentions micro_s or memory_mb, whether they are the measured readings or the budget limits, or how their 0 defaults are interpreted. One sentence of meaning over the two parameters would have closed this gap.

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

Purpose3/5

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

There is a verb ('Flag') and a resource area ('profiler readings over budget'), so the general domain is identifiable as profiling thresholds. However, 'flag' is ambiguous about the actual action (report? error? mutate state?) and nothing distinguishes this from the many other roblox_* diagnostic tools.

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

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites, no indication of where a 'budget' comes from or how it is configured. The agent must guess whether this is a check performed before/after a playtest or a persistent configuration tool.

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