Skip to main content
Glama

studio_run_test

Execute trusted project test code in Studio Run or Play mode with timeout cleanup. Requires RUN_STUDIO_TEST confirmation. Not a sandbox. The managed ModuleScript must return a function.

Instructions

Execute trusted project test code in Studio Run or Play mode with timeout cleanup. Requires RUN_STUDIO_TEST confirmation. Not a sandbox. The managed ModuleScript must return a function.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "modulePath": "<modulePath>",
      "confirmToken": "<confirmToken>"
    },
    "name": "studio_run_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsNo
modeNorun
modulePathYes
confirmTokenYes
timeoutSecondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.3

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does add real signal: timeout cleanup, a confirmation-token gate, and an explicit 'Not a sandbox' safety warning. It omits what happens on timeout failure, whether the code runs with full project privileges, and what the call returns, so the disclosure is partial.

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?

Four short, front-loaded sentences with no filler; the security constraint land early. Slightly telegraphic phrasing ('The managed ModuleScript must return a function') leaves some ambiguity but nothing is wasted.

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?

For a mutation-capable execution tool with a nested args object, no annotations, and no output schema, the description covers safety and the core contract but leaves the args object shape and the return/error behavior unaddressed. Adequate but with clear 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 0%, so the description must compensate for five undocumented parameters. It covers mode ('Studio Run or Play mode'), confirmToken ('Requires RUN_STUDIO_TEST confirmation'), and modulePath ('managed ModuleScript'), but args and timeoutSeconds are only faintly hinted at ('timeout cleanup') and their semantics are not explained.

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?

States a specific verb (execute) and resource (trusted project test code) plus the two execution modes (Run or Play) and the ModuleScript contract. This implicitly separates it from studio_execute_luau, but it never names that sibling, so the differentiator rests on inference.

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?

Gives prerequisites (the RUN_STUDIO_TEST confirmation token, the ModuleScript must return a function) which helps decide if it's callable, but offers no explicit when-to-use-versus-studio_execute_luau-or-studio_start_playtest guidance or exclusions. Usage is implied rather than stated.

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