Skip to main content
Glama
Roblox Studio MCP Gateway

Roblox Studio MCP Gateway

by camilin7483

roblox_breakpoints

List, set, or clear Luau script breakpoints in Roblox Studio to pause playtests and diagnose runtime behavior.

Instructions

List/set/clear script breakpoints.

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

Input Schema

NameRequiredDescriptionDefault
dataNo
actionNolist

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden, yet it discloses almost nothing: it does not say whether breakpoints are keyed by script path and line, whether a session is required, whether clearing is destructive or reversible, or what errors occur on invalid targets. Only the words 'set' and 'clear' hint at mutation.

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?

One front-loaded sentence with no wasted words, but the brevity is under-specification rather than efficiency. It fits the conciseness bar yet leaves the agent without the operational detail a three-mode tool needs.

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

Completeness2/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, but for a multi-mode tool with two undocumented parameters and zero annotations the definition is far too thin. It omits the payload shape for setting breakpoints and the scope of clearing, which are essential to invoking it correctly.

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 adds little: the verbs list/set/clear loosely imply the accepted values of the 'action' parameter, but the free-form 'data' object (which presumably carries breakpoint payloads) is entirely unexplained. An agent cannot tell what to put in 'data' for a set operation.

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 resource (script breakpoints) and three concrete operations (list, set, clear), which is clear enough for an agent to know it is the breakpoint-management tool rather than a script editing tool. It falls short of a 5 because it does not say how the three modes are selected or how this differs from adjacent tools like roblox_script_edit or roblox_playtest.

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?

There is no guidance on when to use this tool versus siblings, no prerequisites (e.g., an active debug/playtest session), and no statement of when setting or clearing breakpoints is appropriate. The only implied usage is that the three verbs exist.

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