Skip to main content
Glama

get_output_log

Read-only

Reads recent Roblox Studio Output window lines, including prints, so you can inspect what scripts printed. Returns newest last and supports filtering by severity.

Instructions

Read recent lines from Studio's Output window, prints included, newest last. Read-only. The plugin keeps the last 1,500 messages, play test output included. Use it to see what a script printed; for errors only, with script and line parsed, get_recent_errors is faster.

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

Input Schema

NameRequiredDescriptionDefault
placeNoTarget place (PlaceId or project name). Defaults to the bound/sole connected place.
severityNoReturn only this message type. Omit for all.
maxEntriesNoHow many of the most recent lines to return. Default 100.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.1
    • addedInput schema / properties / maxEntries / description
      Added value: +"How many of the most recent lines to return. Default 100."
    • addedInput schema / properties / maxEntries / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / maxEntries / minimum
      Added value: +1
    • changedInput schema / properties / maxEntries / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / severity / description
      Added value: +"Return only this message type. Omit for all."
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered (the 'Read-only' sentence is redundant). The description adds genuinely new behavior: a 1,500-message retention buffer, newest-last ordering, and inclusion of play-test output, which tell the agent what data exists and how it is ordered. It stops short of describing entry shape or truncation behavior when the buffer rolls over.

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

Conciseness5/5

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

Three short sentences, front-loaded with what is read and how it is ordered, followed by retention limits and then sibling routing. No wasted wording; the only redundancy is the 'Read-only' clause, which is minor.

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?

For a simple read-only log fetch with full parameter documentation, the description covers source, ordering, retention, and alternatives. With no output schema, it could say more about what each returned entry looks like (e.g. whether severity is attached), but it is sufficient to invoke correctly.

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 100%, so place, severity, and maxEntries are already documented, and the baseline of 3 applies. The description's 'newest last' and 'last 1,500 messages' context loosely informs how maxEntries selects lines, but it adds no syntax or format guidance beyond the schema.

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?

States a specific verb and resource ('Read recent lines from Studio's Output window') plus scope details (prints included, newest last, play test output included). It explicitly distinguishes itself from get_recent_errors, so an agent can choose between the two without opening either schema.

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

Usage Guidelines5/5

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

Provides explicit when-to-use ('to see what a script printed') and names the alternative with the condition that selects it ('for errors only, with script and line parsed, get_recent_errors is faster'). Both the positive case and the exclusion are covered.

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