Skip to main content
Glama
Godot MCP - Full Control
by cxb2523

game_get_logs

Retrieve new print output from a running Godot game since the last call, using an optional cursor and line limit to inspect recent runtime logs.

Instructions

Get new print output from the running game since last call

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum lines returned, defaults to 200
cursorNoOptional absolute cursor from a previous response

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden; it does disclose the important incremental/cursor-like behavior ('since last call'), which is genuinely valuable. It omits whether output is buffered or dropped when unconsumed, whether the call blocks waiting for output, and what happens if no game is running.

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?

A single tight sentence with the key behavioral qualifier ('since last call') front-loaded and no filler. Every word contributes to correct invocation.

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?

There is no output schema, so the description should indicate what a log entry looks like (plain text lines, whether a cursor is returned for the next call). For a simple two-optional-param read tool this is adequate, but the return shape is left entirely implicit.

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 both 'limit' and 'cursor' are already documented in the schema; baseline 3 applies. The description's 'since last call' phrasing loosely connects to the cursor concept but adds no format or semantics beyond the schema.

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 (get) and resource (print output) plus a scope qualifier ('from the running game', 'since last call') that tells the agent this is an incremental tail, not a full dump. It does not, however, distinguish itself from sibling tools like get_debug_output or game_get_errors, which an agent may confuse it with.

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?

'Since last call' implies a polling pattern while a game is running, which is useful implied guidance. There is no explicit statement of when to prefer this over get_debug_output or game_get_errors, and no mention that a game must be running for it to return anything.

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

Deploy Server

Other Tools