Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

get_game_screenshot

Captures a screenshot of the running game viewport for visual inspection, debugging, or sharing the current game state.

Instructions

Capture a screenshot of the running game viewport.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden, and it omits the behaviors that matter most for a capture tool: whether capture pauses the game, whether it requires a running/playing session, and whether repeated calls are rate-limited. It only discloses the target region (game viewport), which is a useful but thin behavioral detail.

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?

A single front-loaded sentence with no filler, and the key scope word ('viewport') is present. It is arguably under-specified rather than over-written, but nothing is wasted.

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

Completeness2/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 explain what the agent receives, yet it never says whether the result is an inline image, base64 payload, or a file path. For a zero-parameter capture tool this single missing fact is the difference between correct and incorrect invocation handling.

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?

The tool takes zero parameters, so the schema baseline applies and there is nothing extra the description needs to document. The description correctly implies the operation is parameterless and self-contained.

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 ('Capture') and resource ('screenshot of the running game viewport'), so an agent knows exactly what is produced and scoped. It does not explicitly differentiate from the sibling get_editor_screenshot, leaving the agent to infer that 'game viewport' vs 'editor' is the dividing line.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no stated precondition that the game must be actively running, and no routing to the closely named alternative get_editor_screenshot. The agent must infer the usage context entirely from the phrase 'running game viewport'.

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