Skip to main content
Glama

console

Read Roblox Studio's Output window and return only new lines since your last call, with errors and warnings flagged. Filter by level, pattern, or datamodel to debug scripts faster.

Instructions

Read Studio's Output window. By default returns only lines that are new since your previous console call (tracked per datamodel). Errors are prefixed [E], warnings [W]. Studio plugin noise is hidden by default.

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

Input Schema

NameRequiredDescriptionDefault
tailNoMax lines returned (most recent). Default 200.
levelNoMinimum level. Default all.
sinceNolast (default): only new lines since the previous call; all: the whole history.
filterNoCase-insensitive substring, or /regex/.
studioNoOptional. Target Studio (name substring, place id or id). Only needed when several Studios are open and none was selected.
contextNoDatamodel to run in. Default: edit when not playing, otherwise server.
include_plugin_noiseNoInclude errors/warnings from installed Studio plugins. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose real behavior: stateful cursor semantics tracked per datamodel, the [E]/[W] line-prefix conventions, and that plugin noise is filtered by default. It does not say whether the call blocks/waits for output, what happens on the first-ever call with no prior cursor, or what a truncated result looks like — but the core behavioral traits are surfaced.

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?

Three tight sentences with the primary purpose front-loaded, and the default-behavior caveat positioned before the formatting details. The final sentence on plugin noise partially restates the 'include_plugin_noise' schema field, so it is efficient but not entirely free of duplication.

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?

There is no output schema, so the description must convey the return shape, and it does at a basic level (output lines, [E]/[W] prefixes, deduplicated incremental view). For a 7-parameter read tool this is close to sufficient, with only truncation/blocking behavior left unstated.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3; the description adds genuine meaning on top by explaining what "new since previous call" means for 'since' and that plugin errors/warnings are excluded unless 'include_plugin_noise' is set. It does not elaborate on 'filter' regex syntax or 'context' datamodel selection, which remain schema-only.

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?

"Read Studio's Output window" names a specific verb and resource, and the following sentences pin down the scope (incremental by default, per datamodel). No sibling in the provided list reads console output, so an agent can identify this tool unambiguously without opening the schema.

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

Usage Guidelines4/5

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

The default incremental behavior ("only lines that are new since your previous console call") tells the agent the intended polling workflow and implies the need to override via 'since' when full history is wanted. It stops short of explicit when-not-to-use guidance or named alternatives, but the domain is narrow enough that this is clear context rather than a gap.

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