Skip to main content
Glama

get_recent_errors

Read-only

Retrieves recent Studio errors and warnings, including play-test events with script and line details. Pass the previous cursor to fetch only new events without waiting on Studio.

Instructions

Read the errors and warnings Studio has produced, including during a play test, with script and line parsed out. Read-only. It reads the feed the plugin already pushed, so it answers instantly even while Studio is busy. Pass the cursor from the previous reply as since to get only new events. For all Output text (prints and info) use get_output_log; for your published game's live servers use get_server_logs.

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

Input Schema

NameRequiredDescriptionDefault
placeNoTarget place (PlaceId or project name). Defaults to the bound/sole connected place.
sinceNoCursor from a previous reply; only events after it are returned. Omit for everything still in the feed.
severityNoReturn only errors or only warnings. Omit for both.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • addedInput schema / properties / severity / description
      Added value: +"Return only errors or only warnings. Omit for both."
    • changedInput schema / properties / since / description
      Previous value: -"only events after this seq cursor (from a prior call)"New value: +"Cursor from a previous reply; only events after it are returned. Omit for everything still in the feed."
  2. First observedv0.1.0

TDQS

A4.5/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, and the description reinforces read-only while adding genuinely new context: it reads a feed the plugin already pushed and therefore answers instantly even while Studio is busy. It does not disclose any feed retention window or event cap, which is the only meaningful gap for a polling tool.

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?

Four compact sentences, front-loaded with what is returned, then provenance/latency, then the cursor workflow, then the sibling disambiguations. Nothing is redundant except a light restatement of the read-only annotation.

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

Completeness5/5

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

For a three-optional-parameter read tool with full schema coverage, an annotation safety profile, and no output schema, the description provides everything needed: data source, latency behavior, incremental polling pattern, and explicit alternatives. No return-value documentation is required since no output schema exists and the description already notes script/line parsing.

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 coverage is 100%, so the schema already documents place, since, and severity. The description adds practical meaning for 'since' by explaining it is the cursor from a previous reply, but says nothing extra about place resolution or severity semantics beyond the schema's own text. Baseline 3 applies when the schema carries the detail.

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 the errors and warnings Studio has produced') plus concrete scope ('including during a play test, with script and line parsed out'). It explicitly names the two sibling tools it is not (get_output_log, get_server_logs), so an agent can route without opening any 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?

Gives explicit when-to-use guidance with alternatives: get_output_log for prints/info Output text, get_server_logs for a published game's live servers. It also states how to use the cursor for incremental polling, so both selection and call pattern are covered.

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